Wireless Communication Method

ABSTRACT

A wireless communication method implemented by a transmission user equipment includes receiving first secondary carrier status indication information from a network device, where the first secondary carrier status indication information indicates that each of a plurality of secondary carriers is in an activated state or a deactivated state, the plurality of secondary carriers are used for multi-carrier sidelink communication between the transmission user equipment and at least one reception user equipment, and each reception user equipment corresponds to at least one secondary carrier; sending second secondary carrier status indication information to each reception user equipment, where the second secondary carrier status indication information indicates that each of the at least one secondary carrier is in an activated state or a deactivated state; and when acknowledgment information is received from one or more reception user equipments, sending secondary carrier setting complete information to the network device.

This application claims priority to Chinese Patent Application No.202010450929.X, filed with the China National Intellectual PropertyAdministration on May 25, 2020 and entitled “WIRELESS COMMUNICATIONMETHOD”, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

One or more embodiments of this application usually relate to thecommunications field, and specifically, to wireless communicationmethods applied to transmission user equipment and a network device. Themethod can implement activation or deactivation effective indication ofa plurality of carriers used for multi-carrier sidelink communicationbetween transmission user equipment and reception user equipment.

BACKGROUND

In a 5G new radio (new radio, NR) vehicle to everything (vehicle toeverything, V2X) scenario, for V2X communication between transmissionuser equipment (transmission UE, Tx UE) and reception user equipment(reception UE, Rx UE), there are currently two resource allocationmodes: a base station scheduled resource allocation mode and a Tx UEautonomous resource selection allocation mode. In the base stationscheduled resource allocation mode, Tx UE requests a communicationresource from a base station, and the base station allocates a dedicatedresource to the Tx UE to transmit control information and datainformation. In the Tx UE autonomous resource selection allocation mode,a base station configures a resource pool for Tx UE, and the Tx UEautonomously selects a resource from the resource pool to send controlinformation and data information.

In an existing NR-V2X technical solution, V2X communication between TxUE and Rx UE supports only a single carrier. For example, in the basestation scheduled resource allocation mode, after the Tx UE and the RxUE complete a V2X sidelink communication connection, when the Tx UE hasa data transmission requirement, the Tx UE reports, to the base station,a scheduling request (scheduling request, SR) and a buffer status report(buffer status report, BSR) that indicates a size of an amount ofto-be-transmitted data, and the base station schedules a single-carrierrelated data transmission resource for the Tx UE based on the SR and theBSR However, because a single-carrier data transmission capability islimited, communication quality of the Tx UE is limited when the Tx UEhas a large data communication requirement.

SUMMARY

The following describes this application from a plurality of aspects.For implementations and beneficial effects of the following plurality ofaspects, refer to each other.

A first aspect of this application provides a wireless communicationmethod applied to transmission user equipment (Tx UE), and the methodincludes: receiving first secondary carrier (SCell) status indicationinformation from a network device, where the first secondary carrierstatus indication information indicates that each of a plurality ofsecondary carriers is in an activated state or a deactivated state, theplurality of secondary carriers are used for multi-carrier sidelinkcommunication between the transmission user equipment and at least onereception user equipment, and each of the at least one reception userequipment corresponds to at least one of the plurality of secondarycarriers;

sending second secondary carrier status indication information to eachreception user equipment, where the second secondary carrier statusindication information indicates that each of the at least one secondarycarrier is in an activated state or a deactivated state; and

when acknowledgment information is received from one or more of the atleast one reception user equipment, sending secondary carrier settingcomplete information to the network device, where the acknowledgmentinformation is used to indicate that the one or more reception userequipments have received the second secondary carrier status indicationinformation, and the secondary carrier setting complete information isused to indicate that each of the one or more reception user equipmentshas completed corresponding setting on the at least one secondarycarrier.

In some embodiments, the method further includes: when theacknowledgment information is not received from the one or morereception user equipments, sending secondary carrier setting incompleteinformation to the network device, where the secondary carrier settingincomplete information is used to partially indicate at least that theone or more reception user equipments do not complete the correspondingsetting in response to the second secondary carrier status indicationinformation.

In some embodiments, the method further includes: receiving firstmulti-carrier configuration information from the network device, wherethe first multi-carrier configuration information indicates informationrelated to the plurality of secondary carriers configured by the networkdevice, and the first multi-carrier configuration information includesan identifier of each reception user equipment and an identifier of theat least one secondary carrier corresponding to each reception userequipment in the plurality of secondary carriers; and

sending second multi-carrier configuration information to each receptionuser equipment based on the first multi-carrier configurationinformation, where the second multi-carrier configuration informationincludes the identifier of the at least one secondary carriercorresponding to each reception user equipment.

In some embodiments, when the one or more reception user equipmentsinclude a plurality of reception user equipments, the secondary carriersetting complete information includes a first bitmap part that is usedto indicate an index or a destination layer-2 identifier of each of theplurality of reception user equipments and a second bitmap part that isused to indicate that each of the plurality of reception user equipmentshas completed the corresponding setting.

In some embodiments, a total quantity of bits in the first bitmap partis related to a maximum quantity of reception user equipments supportedby the transmission user equipment, a plurality of bits in the firstbitmap are in a one-to-one correspondence with the plurality ofreception user equipments, and the correspondence between the pluralityof bits and the plurality of reception user equipments is related to theindex of each of the plurality of reception user equipments.

In some embodiments, the second bitmap part includes a plurality of bitrows corresponding to the plurality of reception user equipments, andeach of the plurality of reception user equipments corresponds to atleast one of the plurality of bit rows.

The at least one bit row includes at least one bit, the at least one bitis in a one-to-one correspondence with the at least one secondarycarrier, a value of each of the at least one bit indicates that eachreception user equipment has completed the corresponding setting, andthe corresponding setting is performed on a secondary carriercorresponding to each bit in the at least one secondary carrier.

In some embodiments, a total quantity of bits included in the at leastone bit row is related to a maximum quantity of secondary carrierssupported by each reception user equipment or the transmission userequipment.

In some embodiments, the correspondence between the at least one bit inthe at least one bit row and the at least one secondary carrier isrelated to an arrangement order of the identifier of the at least onesecondary carrier in the first multi-carrier configuration information,or is related to an index of each of the at least one secondary carrierin the plurality of secondary carriers.

In some embodiments, the secondary carrier setting complete informationof reception user equipment setting complete information includes asecondary carrier setting complete bitmap that is used to indicate thateach of the one or more reception user equipments has completed thecorresponding setting.

In some embodiments, the secondary carrier setting complete bitmapincludes at least one bitmap part, the at least one bitmap part is in aone-to-one correspondence with the one or more reception userequipments, each of the at least one bitmap part includes at least onebit, the at least one bit is in a one-to-one correspondence with the atleast one secondary carrier, a value of each of the at least one bitindicates that reception user equipment corresponding to each bitmappart has completed the corresponding setting, and the correspondingsetting is performed on a secondary carrier corresponding to each bit inthe at least one secondary carrier.

In some embodiments, a total quantity of bits in the at least one bitpart is related to a total quantity of secondary carriers correspondingto the one or more reception user equipments, and the total quantity ofsecondary carriers corresponding to the one or more reception userequipments is equal to a sum of quantities of the at least one secondarycarrier corresponding to all the reception user equipments.

In some embodiments, an arrangement order of each bitmap part in theactivation or deactivation setting bitmap is related to an arrangementorder of the identifier of each reception user equipment in the firstmulti-carrier configuration information, and the correspondence betweenthe at least one bit in each bitmap part and the at least one secondarycarrier is related to an arrangement order of the identifier of the atleast one secondary carrier in the first multi-carrier configurationinformation.

In some embodiments, the secondary carrier setting complete informationincludes identifiers of the one or more reception user equipments andidentifiers of secondary carriers for which the one or more receptionuser equipments have completed the corresponding setting for theactivated state or the deactivated state, or includes identifiers ofsecondary carriers for which the one or more reception user equipmentshave completed the corresponding setting for the activated state or thedeactivated state.

In some embodiments, the corresponding setting includes: performingmonitoring setting on a secondary carrier, in the at least one secondarycarrier, that is indicated to be in an activated state in the secondsecondary carrier status indication information, and/or performingde-monitoring setting on a secondary carrier, in the at least onesecondary carrier, that is indicated to be in a deactivated state in thesecond secondary carrier status indication information.

A second aspect of this application provides a wireless communicationmethod applied to a network device, and the method includes:

generating first secondary carrier status indication information, wherethe first secondary carrier status indication information indicates thateach of a plurality of secondary carriers is in an activated state or adeactivated state, the plurality of secondary carriers are used formulti-carrier sidelink communication between transmission user equipmentand at least one reception user equipment, and each of the at least onereception user equipment corresponds to at least one of the plurality ofsecondary carriers: sending the first secondary carrier statusindication information to the transmission user equipment (Tx UE); andreceiving secondary carrier setting complete information from thetransmission user equipment, where the secondary carrier settingcomplete information is used to indicate that each of one or morereception user equipments has completed corresponding setting on the atleast one secondary carrier, and the at least one reception userequipment includes the one or more reception user equipments.

In some embodiments, the method further includes:

sending first multi-carrier configuration information to thetransmission user equipment, where the first multi-carrier configurationinformation indicates information related to the plurality of secondarycarriers configured by the network device, and the first multi-carrierconfiguration information includes an identifier of each reception userequipment and an identifier of the at least one secondary carriercorresponding to each reception user equipment in the plurality ofsecondary carriers.

In some embodiments, when the one or more reception user equipmentsinclude a plurality of reception user equipments, the secondary carriersetting complete information includes a first bitmap part that is usedto indicate an index or a destination layer-2 identifier of each of theplurality of reception user equipments and a second bitmap part that isused to indicate that each of the plurality of reception user equipmentshas completed the corresponding setting.

In some embodiments, a total quantity of bits in the first bitmap partis related to a maximum quantity of reception user equipments supportedby the transmission user equipment, a plurality of bits in the firstbitmap are in a one-to-one correspondence with the plurality ofreception user equipments, and the correspondence between the pluralityof bits and the plurality of reception user equipments is related to theindex of each of the plurality of reception user equipments.

In some embodiments, the second bitmap part includes a plurality of bitrows corresponding to the plurality of reception user equipments, andeach of the plurality of reception user equipments corresponds to atleast one of the plurality of bit rows.

The at least one bit row includes at least one bit, the at least one bitis in a one-to-one correspondence with the at least one secondarycarrier, a value of each of the at least one bit indicates that eachreception user equipment has completed the corresponding setting, andthe corresponding setting is performed on a secondary carriercorresponding to each bit in the at least one secondary carrier.

In some embodiments, a total quantity of bits included in the at leastone bit row is related to a maximum quantity of secondary carrierssupported by each reception user equipment or the transmission userequipment.

In some embodiments, the correspondence between the at least one bit inthe at least one bit row and the at least one secondary carrier isrelated to an arrangement order of the identifier of the at least onesecondary carrier in the first multi-carrier configuration information,or is related to an index of each of the at least one secondary carrierin the plurality of secondary carriers.

In some embodiments, the secondary carrier setting complete informationof reception user equipment setting complete information includes asecondary carrier setting complete bitmap that is used to indicate thateach of the one or more reception user equipments has completed thecorresponding setting.

In some embodiments, the secondary carrier setting complete bitmapincludes at least one bitmap part, the at least one bitmap part is in aone-to-one correspondence with the one or more reception userequipments, each of the at least one bitmap part includes at least onebit, the at least one bit is in a one-to-one correspondence with the atleast one secondary carrier, a value of each of the at least one bitindicates that reception user equipment corresponding to each bitmappart has completed the corresponding setting, and the correspondingsetting is performed on a secondary carrier corresponding to each bit inthe at least one secondary carrier.

In some embodiments, a total quantity of bits in the at least one bitpart is related to a total quantity of secondary carriers correspondingto the one or more reception user equipments, and the total quantity ofsecondary carriers corresponding to the one or more reception userequipments is equal to a sum of quantities of the at least one secondarycarrier corresponding to all the reception user equipments.

In some embodiments, an arrangement order of each bitmap part in theactivation or deactivation setting bitmap is related to an arrangementorder of the identifier of each reception user equipment in the firstmulti-carrier configuration information, and the correspondence betweenthe at least one bit in each bitmap part and the at least one secondarycarrier is related to an arrangement order of the identifier of the atleast one secondary carrier in the first multi-carrier configurationinformation.

In some embodiments, the secondary carrier setting complete informationincludes identifiers of the one or more reception user equipments andidentifiers of secondary carriers for which the one or more receptionuser equipments have completed the corresponding setting for theactivated state or the deactivated state, or includes identifiers ofsecondary carriers for which the one or more reception user equipmentshave completed the corresponding setting for the activated state or thedeactivated state.

In some embodiments, the corresponding setting includes: performingmonitoring setting on a secondary carrier, in the at least one secondarycarrier, that is indicated to be in an activated state, and/orperforming de-monitoring setting on a secondary carrier, in the at leastone secondary carrier, that is indicated to be in a deactivated state.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1A is a schematic diagram of an application scenario according toan embodiment of this application;

FIG. 1B is a schematic diagram of another application scenario accordingto an embodiment of this application;

FIG. 2 is a schematic flowchart of a wireless communication method 200according to an embodiment of this application;

FIG. 3A to FIG. 3C are a schematic flowchart of a wireless communicationmethod 300 according to an embodiment of this application;

FIG. 4A shows an example structure of a MAC subheader corresponding to asidelink SCell setup complete MAC CE according to an embodiment of thisapplication;

FIG. 4B shows another example structure of a MAC subheader correspondingto a sidelink SCell setup complete MAC CE according to an embodiment ofthis application;

FIG. 5 shows an example of carrier allocation at a network device 120according to an embodiment of this application;

FIG. 6A is a schematic diagram of a structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 6B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that Rx UE 130 ain FIG. 5 has completed corresponding setting on a correspondingsecondary carrier according to FIG. 6A;

FIG. 6C is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 7A is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 7B is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 7C is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 8A is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 8B is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 9A is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 9B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that Rx UE 130 a,Rx UE 130 b, and Rx UE 130 n in FIG. 5 have completed correspondingsetting on corresponding secondary carriers according to FIG. 9A;

FIG. 9C is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 9D is a schematic diagram of another structure of secondary carriersetting complete information according to an embodiment of thisapplication;

FIG. 10A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 10B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 11A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 11B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 12A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 12B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 13 shows an example of carrier allocation at a network device 120according to an embodiment of this application;

FIG. 14A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 14B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that Rx UE 130 ain FIG. 18 has completed corresponding setting on a correspondingsecondary carrier according to FIG. 19A;

FIG. 14C is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 15A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 15B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 15C is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 16A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 16B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 17A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 17B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that Rx UE 130 a,Rx UE 130 b, and Rx UE 130 n in FIG. 13 have completed correspondingsetting on corresponding secondary carriers according to FIG. 17A;

FIG. 17C is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 18A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 18B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 19A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 19B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 20A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 20B is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 21 shows another example of carrier allocation at a network device120 according to an embodiment of this application;

FIG. 22A is a schematic diagram of another structure of secondarycarrier setting complete information according to an embodiment of thisapplication;

FIG. 22B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that Rx UE 130 a,Rx UE 130 b, and Rx UE 130 n in FIG. 21 have completed correspondingsetting on corresponding secondary carriers according to FIG. 22A;

FIG. 22C is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that Rx UE 130 aand Rx UE 130 n in FIG. 21 have completed corresponding setting oncorresponding secondary carriers according to FIG. 22A;

FIG. 23A and FIG. 23B are a schematic flowchart of a wirelesscommunication method 2300 applied to Tx UE 110 according to anembodiment of this application;

FIG. 24 is a schematic flowchart of a wireless communication method 2400applied to a network device 120 according to an embodiment of thisapplication;

FIG. 25 is a schematic flowchart of a wireless communication method 2500applied to Rx UE 130 according to an embodiment of this application; and

FIG. 26 is a schematic diagram of a structure of a device 2600 accordingto an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

It should be understood that, although terms such as “first” and“second” may be used in this specification to describe various features,these features should not be limited by these terms. These terms aremerely used for distinguishing, and shall not be understood as anindication or implication of relative importance. For example, withoutdeparting from the scope of example embodiments, a first feature may bereferred to as a second feature, and similarly the second feature may bereferred to as the first feature.

Unless otherwise stated, terms “contain”, “have”, and “include” aresynonymous. A phrase “A/B” indicates “A or B”. A phrase “A and/or B”means “(A), (B), or (A and B)”.

As used herein, a term “module” may mean being a part thereof, orinclude a memory (a shared memory, a special-purpose memory, or a groupmemory) for running one or more software or firmware programs, anapplication-specific integrated circuit (ASIC), an electronic circuitand/or a processor (a shared processor, a special-purpose processor, ora group processor), a combined logic circuit, and/or another appropriatecomponent that provides the function.

To make the objectives, technical solutions, and advantages of thisapplication clearer, the following further describes implementations ofthis application in detail with reference to the accompanying drawings.

FIG. 1A and FIG. 1B show two application scenarios according toembodiments of this application. A related communications systemincludes Tx UE 110, a network device 120, and Rx UE 130 a to Rx UE 130 n(collectively referred to as Rx UE 130 in the following embodiments).When the Tx UE 110 needs to communicate with the neighboring Rx UE 130 ato Rx UE 130 n, the Tx UE 110 may first request, from the network device120, resources required for communication, and then send controlinformation and data information to the Rx UE 130 a to the Rx UE 130 nbased on the resources allocated by the network device. A differencebetween FIG. 1A and FIG. 1B is that, in FIG. 1A, the Tx UE 110 and theRx UE 130 a to the Rx UE 130 n are all located within coverage of thenetwork device 120, while in FIG. 1B, the Tx UE 110 and some Rx UEs 130(for example, the Rx UE 130 a and the Rx UE 130 b) are located withinthe coverage of the base station 120, and the other Rx UEs 130 (forexample, the Rx UE 130 n) are located outside the coverage of thenetwork device 120. It should be noted that, in FIG. 1B, the Rx UE 130 ato the Rx UE 130 n may alternatively be all located outside the coverageof the network device 120. In addition, although FIG. 1A and FIG. 1Bshow a case in which the Tx UE 110 can communicate with the Rx UE 130 ato the Rx UE 130 n, the Tx UE 110 can communicate with any quantity ofRx UEs 130.

In FIG. 1A and FIG. 1B: (1) The Tx UE 110 and the Rx UE 130 are userequipments, are also referred to as terminals or terminal devices, andare devices providing voice and/or data connectivity for a user. Commonterminal devices include, for example, a vehicle-mounted device, amobile phone, a tablet computer, a notebook computer, a palmtopcomputer, a mobile internet device (mobile internet device, MID), awearable device (for example, including a smartwatch, a smart band, or apedometer), a personal digital assistant, a portable media player, anavigation device, a video game device, a set-top box, a virtual realitydevice and/or an augmented reality device, an internet of things device,an industrial control device, a streaming media client device, ane-book, a reading device, a POS terminal, and other devices.

(2) The network device 120 is also referred to as a radio access network(Radio Access Network, RAN) device, is a device that communicates withuser equipment through a radio access network, and includes networkdevices in various communications standards, for example, includes butis not limited to a base station, an evolved NodeB (evolved NodeB, eNB),a radio network controller (radio network controller, RNC), a NodeB(NodeB, NB) a next generation NodeB (next generation NodeB, gNB), a basestation controller (Base Station Controller, BSC), a base transceiverstation (Base Transceiver Station, BTS), a home network device (forexample, Home evolved NodeB or Home NodeB, HNB), and a baseband unit(Baseband Unit, BBU). The network device includes network devices invarious frequency standards, for example, includes but is not limited toa low-frequency network device and a high-frequency network device.

(3) Communication between the Tx UE 110 and the Rx UE 130 may includesidelink communication (sidelink communication), and sidelinkcommunication may include proximity-based services (proximity-basedservices, ProSe) direct communication (defined in 3GPP TS 23.303), V2Xcommunication (defined in 3GPP TS 23.285), and other types of wirelesscommunication directly performed between two or more neighboring userequipments.

(4) In sidelink communication, a communication link between the Tx UE110 and the Rx UE 130 is referred to as a sidelink (sidelink), and acommunications interface between the Tx UE 110 and the Rx UE 130 isreferred to as a PC5 interface.

(5) Communication between the Tx UE 110 and the network device 120 maybe based on, but is not limited to, a 3rd generation (3rd Generation,3G) mobile communications system, a 4th generation (4th Generation, 4G)mobile communications system, a 5th generation (5th generation, 5G)system, a new radio (new radio, NR) system or a communications systemhaving a same architecture as the 5G system, and other subsequent mobilecommunications systems.

In the conventional technology, in 5G NR, sidelink communication betweenthe Tx UE 110 and the Rx UE 130 supports only a single carrier, and aresource configured by the network device 120 for the Tx UE 110 forsidelink communication includes only a single-carrier resource. In thiscase, if the Tx UE 110 has a large data communication requirement,communication quality of the Tx UE 110 may be limited. In addition, in4G LTE V2X, although sidelink communication between the Tx UE 110 andthe Rx UE 130 already supports a plurality of carriers, the plurality ofcarriers are only for a broadcast scenario. In other words, the Tx UE110 sends broadcast data on a plurality of carriers configured by thenetwork device 120, and Rx UE 130 of interest performs monitoring.

In a long term evolution (long term evolution, LTE) system, to meetrequirements for increasing a single-user peak rate and a systemcapacity, a carrier aggregation (carrier aggregation. CA) technology isintroduced. The CA technology can aggregate a plurality of LTE componentcarriers (component carrier, CC) to effectively increase anuplink/downlink transmission rate. A component carrier accessed by UE isreferred to as a primary carrier, and another component carrier isreferred to as a secondary carrier. An uplink carrier and acorresponding downlink carrier form a cell (Cell). Correspondingly, aprimary carrier is a primary cell (Primary Cell, PCell), and a secondarycarrier is a secondary cell (Secondary Cell, SCell).

However, even if the CA technology in the LTE system is used forsidelink communication between the Tx UE 110 and the Rx UE 130, becausethe network device 120 cannot indicate activated states or deactivatedstates of a plurality of carriers in the conventional technology, when aplurality of carriers are configured for the Rx UE 130, only allsecondary cells (secondary cell. SCell) can be continuously monitored.Consequently, power consumption of the Rx UE is excessively high.

In embodiments of this application, the network device 120 may configurea plurality of carriers for sidelink communication between the Tx UE 110and one or more Rx UEs 130 based on a request of the Tx UE 110, andindicate activated states or deactivated states of the plurality ofcarriers to the Tx UE 110; the Tx UE 110 may indicate an activated stateor a deactivated state of a related carrier to the one or more Rx UEs130 based on information about the network device 120; the Rx UE 130 mayperform setting on the related carrier based on information about the TxUE 110, and feed back acknowledgment information to the Tx UE 110; andthe Tx UE 110 may send reception user equipment carrier setting completeinformation to the network device 120, to indicate that the Rx UE 130has completed setting on the related carrier.

In embodiments of this application, resources used by the Tx UE 110 forsidelink communication increase. Even if the Tx UE 110 has a large datacommunication requirement, communication quality of the Tx UE 110 can beensured, and a carrier activation or deactivation mechanism can alsobetter manage battery consumption of the Rx UE 130.

In addition, if the network device 120 starts data scheduling before theRx UE 130 completes setting on a corresponding carrier, the Rx UE 130cannot obtain data from the Tx UE 110 through monitoring, causing awaste of resources. However, in embodiments of this application, thenetwork device 120 starts data scheduling after receiving reception userequipment carrier setting complete information from the Tx UE 110, sothat the foregoing problem can be avoided.

The following uses specific embodiments to describe in detail thetechnical solutions of this application and a manner of resolving theforegoing technical problem by using the technical solutions of thisapplication. The following specific embodiments may be mutuallycombined, and same or similar concepts or processes are not repeatedlydescribed in some embodiments.

FIG. 2 is a schematic flowchart of a wireless communication method 200according to an embodiment of this application. As shown in FIG. 2 , thewireless communication method 200 may include the following steps.

S201: A network device 120 sends first secondary carrier statusindication information to Tx UE 110.

In an example, the first secondary carrier status indication informationindicates that each of a plurality of secondary carriers is in anactivated state or a deactivated state, the plurality of secondarycarriers are used for multi-carrier sidelink communication between theTx UE 110 and at least one Rx UE 130, and each of the at least one Rx UE130 corresponds to at least one of the plurality of secondary carriers.

S202: Send second secondary carrier status indication information toeach of the at least one Rx UE 130 in S201, for example, in S202 a, sendthe second secondary carrier status indication information to Rx UE 130a; and in S202 n, send the second secondary carrier status indicationinformation to Rx UE 130 n.

In an example, the second secondary carrier status indicationinformation indicates that each of the at least one secondary carrier inS201 is in an activated state or a deactivated state.

S203: One or more Rx UEs 130 that receive the second secondary carrierstatus indication information send acknowledgment information to the TxUE 110, to indicate, to the Tx UE 110, that the one or more Rx UEs 130have received the second secondary carrier status indication informationfrom the Tx UE 110.

S204: The Tx UE 110 sends secondary carrier setting complete informationto the network device 120, to indicate, to the network device 120, thatone or more Rx UEs 130 have completed corresponding setting oncorresponding secondary carriers in response to the second secondarycarrier status indication information.

In an example, the one or more Rx UEs 130 may include the Rx UEs 130from which the Tx UE 110 receives the acknowledgment information.

In an example, the secondary carrier setting complete information may berelated to numbers of the plurality of secondary carriers in S201 at thenetwork device 120. For a numbering rule of the plurality of secondarycarriers at the network device 120, refer to that shown in FIG. 5 , FIG.13 , or FIG. 21 in the following embodiment. For a structure of thesecondary carrier setting complete information related to the numbers ofthe plurality of secondary carriers at the network device 120, refer tothat shown in FIG. 6A to FIG. 12B, FIG. 14A to FIG. 20B, or FIG. 22A toFIG. 22C in the following embodiment.

FIG. 3A to FIG. 3C are a schematic flowchart of a wireless communicationmethod 300 according to an embodiment of this application. It should benoted that, although steps of the method are presented in a particularorder in this embodiment of this application, the order of the steps maybe changed in different embodiments. As shown in FIG. 3A to FIG. 3C, thewireless communication method 300 may include the following steps.

S301: Tx UE 110 sends sidelink communication requirement indicationinformation to a network device 120.

In an example, the Tx UE 110 may send the sidelink communicationrequirement indication information to the network device 120 by usingany one of a SidelinkUEInformation message and a SidelinkUEInformationNRmessage defined in 3rd Generation Partnership Project (3rd GenerationPartnership Project, 3GPP) TS 36.331 and a SidelinkUEInformationEUTRAmessage and a SidelinkUEInformationNR message message defined in TS38.331 (which are collectively referred to as a SidelinkUEInformationtype message below).

The SidelinkUEInformation type message is used by user equipment toindicate sidelink-related information to a network device (for example,a base station). In the SidelinkUEInformation type message, the sidelinkcommunication requirement indication information may include informationindicating a frequency of interest of the user equipment that is used totransmit and receive sidelink communication, destination list indicationinformation, and the like. The destination list indication informationmay include information indicating identifiers (for example but notlimited to, destination layer-2 identifiers (destination layer-2 ID)defined in 3GPP TS 36.300) of one or more Rx UEs 130 (for example butnot limited to, Rx UE 130 a to Rx UE 130 n).

S302: The network device 120 sends, to the Tx UE 110, informationindicating that a resource allocation mode of the Tx UE 110 is a networkdevice scheduled resource allocation mode.

In an example, the network device 120 may send, by using a secondmessage, the information indicating that the resource allocation mode ofthe Tx UE 110 is the network device scheduled resource allocation mode,where the second message may be higher layer signaling, for example, RRCsignaling. For example, the second message may include anRRCConnectionReconfiguration message defined in 3GPP TS 36.331 or anRRCReconfiguration message defined in 3GPP TS 38.331. In theRRCConnectionReconfiguration message or the RRCReconfiguration message,content of an information element (information element, IE)“SL-V2X-ConfigDedicated” may indicate that the resource allocation modeof the Tx UE 110 is a base station scheduled resource allocation mode oran autonomous resource selection allocation mode.

S303: The Tx UE 110 sends, to the network device 120, information forrequesting resources required for sidelink connection establishment.

In an example, the information for requesting resources required forsidelink connection establishment may include a scheduling request(scheduling request, SR) and a buffer status report (buffer statusreport, BSR). The SR is used by the Tx UE 110 to indicate, to thenetwork device 120, that the Tx UE 110 has data to be transmitted, andthe BSR is used by the Tx UE 110 to indicate, to the network device 120,an amount of data to be transmitted by the Tx UE 110.

It can be understood that the SR and the BSR may be separately sent, ormay be simultaneously sent. This is not limited in this embodiment ofthis application.

S304: The network device 120 sends, to the Tx UE 110, informationindicating resources scheduled for the Tx UE 110.

These resources are used by the Tx UE 110 to establish sidelinkconnections to one or more Rx UEs 130, for example but not limited to,the Rx UE 130 a to the Rx UE 130 n.

In an example, the network device 120 may perform resource schedulingbased on the BSR reported by the Tx UE 110.

In an example, the network device 120 may send, to the Tx UE 110 througha PDCCH, the information indicating the resources scheduled by thenetwork device 120 for the Tx UE 110.

In an example, for each of the one or more Rx UEs 130, the networkdevice 120 allocates a single-carrier resource corresponding to the RxUE 130, where the single-carrier resource is used by the Tx UE 110 toestablish a sidelink connection to the Rx UE 130.

S305: The Tx UE 110 sends sidelink connection establishment requestinformation to the one or more Rx UEs 130 based on the resourcesallocated by the network device 120.

For example, in S305 a, the Tx UE 110 sends, to the Rx UE 130 a,information for requesting to establish a sidelink connection; and inS305 n, the Tx UE 110 sends, to the Rx UE 130 n, information forrequesting to establish a sidelink connection on a PC5 interface.

It can be understood that the Tx UE 110 may simultaneously orsequentially send the sidelink connection establishment requestinformation to the one or more Rx UEs 130. This is not limited in thisembodiment of this application.

It should be noted that, for each Rx UE 130, the Tx UE 110 uses a singlecarrier that is allocated by the network device 120 and that correspondsto the Rx UE 130 as a primary carrier (or referred to as a primarycell), where the primary carrier is a carrier used to establish asidelink connection between the Tx UE 110 and the Rx UE 130. Inaddition, the Tx UE 110 may perform setting based on the informationindicating the resources scheduled by the network device 120 for the TxUE 110, to perform sidelink communication on the single carrier. Forexample, the Tx UE 110 may add the single carrier corresponding to anidentifier of the single carrier based on a parameter configuration ofthe single carrier.

S306: The one or more Rx UEs 130 send sidelink connection establishmentcomplete indication information to the Tx UE 110.

For example, in S306 a, the Rx UE 130 a sends the sidelink connectionestablishment complete indication information to the Tx UE 110; and inS306 n, the Rx UE 130 n sends the sidelink connection establishmentcomplete indication information to the Tx UE 110.

S307: When the Tx UE 110 has data to be transmitted to the Rx UE 130,the Tx UE 110 may send sidelink radio bearer establishment requestinformation and multi-carrier configuration request information to thenetwork device 120.

In an example, the Tx UE 110 may send the foregoing information by usinga third message, where the third message may include aSidelinkUEInformation type message.

In an example, in the SidelinkUEInformation type message, the Tx UE 110may use 1 bit to indicate whether the Tx UE 110 requests a multi-carrierconfiguration from the network device 120. When a value of the bit is“1”, it indicates that the Tx UE 110 requests the multi-carrierconfiguration from the network device 120, that is, the value “1” is theforegoing multi-carrier configuration request information; or when avalue of the bit is 0, it indicates that the Tx UE 110 does not requestthe multi-carrier configuration from the network device 120.Alternatively, when a value of the bit is “0”, it indicates that the TxUE 110 requests the multi-carrier configuration from the network device120, that is, the value “0” is the foregoing multi-carrier configurationrequest information; or when a value of the bit is 1, it indicates thatthe Tx UE 110 does not request the multi-carrier configuration from thenetwork device 120.

In another example, the multi-carrier configuration request informationmay further include identifiers of one or more Rx UEs 130, to indicate,to the network device 120, Rx UEs 130 in sidelink communication that iswith the Tx UE 110 and for which the network device 120 needs toconfigure a plurality of carriers. The identifier of the Rx UE 130 mayinclude but is not limited to a destination layer-2 identifier(destination layer-2 ID) of the Rx UE 130, an index of the Rx UE 130 inthe one or more Rx UEs communicating with the Tx UE 110, and the like.

The Tx UE 110 and the network device 120 may determine, based on thedestination list indication information in S301 by using a default rule,an index of Rx UE 130 in the one or more Rx UEs communicating with theTx UE 110. For example, in the destination list indication information,the Tx UE 110 and the network device 120 may consider, by default, thatan index of Rx UE 130 whose identifier ranks first is 1, an index of RxUE 130 whose identifier ranks second is 2, and so on. Alternatively, theTx UE 110 may directly indicate an index of Rx UE 130 in the destinationlist indication information in S301.

It should be noted that the Tx UE 110 may alternatively not send themulti-carrier configuration request information to the network device120, but the network device 120 determines whether a plurality ofcarriers need to be configured for the Tx UE 110.

S308: The network device 120 sends information indicating a radio bearerconfigured for the Tx UE 110 and first multi-carrier configurationinformation to the Tx UE 110.

The first multi-carrier configuration information is used to indicateinformation related to a plurality of secondary carriers configured bythe network device 120, and the plurality of secondary carriers are usedfor multi-carrier sidelink communication (that is, sidelinkcommunication based on a plurality of carriers, where the plurality ofcarriers include a primary carrier and a secondary carrier) between theTx UE 110 and one or more Rx UEs 130. In addition, a difference betweenthe secondary carrier and the primary carrier is that the secondarycarrier is a carrier for providing additional radio resources forsidelink communication between the Tx UE 110 and the Rx UE 130.

In an example, the network device 120 may send the foregoing informationby using a fourth message, where the fourth message includes anRRCConnectionReconfiguration message defined in 3GPP TS 36.331, anRRCReconfiguration message defined in 3GPP TS 38.331, or a new messagethat is not defined in 3GPP TS.

In an example, the first multi-carrier configuration information mayinclude identifiers of the one or more Rx UEs 130 and an identifier ofat least one secondary carrier corresponding to each Rx UE 130 in theplurality of secondary carriers, and the at least one secondary carriercorresponding to each Rx UE 130 is used for multi-carrier sidelinkcommunication between the Tx UE 110 and the Rx UE 130. The identifier ofthe Rx UE 130 may include but is not limited to a destination layer-2identifier (destination layer-2 ID) or an index of the Rx UE 130, andthe index of the Rx UE 130 may include but is not limited to an index ofeach Rx UE 130 included in the foregoing destination list indicationinformation, an index of each Rx UE 130 included in the foregoingmulti-carrier configuration request information, an index of each Rx UE130 having established a sidelink connection to the Tx UE 110, and thelike. The identifier of the secondary carrier may include but is notlimited to a secondary carrier identifier (Identifier, ID), a cellindex, and the like.

In addition, for each secondary carrier, the first multi-carrierconfiguration information may further include a parameter configurationof the secondary carrier, for example, a frequency band, a frequency, abandwidth, or a subcarrier spacing.

In another example, the identifier of the secondary carrier may furtherinclude a number of each secondary carrier, and the number of thesecondary carrier may be used by the Tx UE 110 to indicate secondarycarrier setting complete information to the network device 120 in S317.However, when the Tx UE 110 and the network device 120 may determine thenumber of each secondary carrier by using a default rule, the firstmulti-carrier configuration information may alternatively not includethe number of each secondary carrier. Details are described in thefollowing embodiment.

It should be noted that, when the Tx UE 110 does not send themulti-carrier configuration request information to the network device120, the network device 120 may determine whether the plurality ofcarriers need to be configured for the Tx UE 110. For example, thenetwork device 120 may determine, based on historical resource usage ofthe Tx UE 110 and current idle resources, whether the plurality ofcarriers need to be configured for the Tx UE 110.

S309: The Tx UE 110 sends second multi-carrier configuration informationto one or more Rx UEs 130.

For example, in S309 a, the Tx UE 110 sends the second multi-carrierconfiguration information to the Rx UE 130 a; and in S309 n, the Tx UE110 sends the second multi-carrier configuration information to the RxUE 130 n.

It can be understood that the Tx UE 110 may simultaneously orsequentially send the second multi-carrier configuration information tothe one or more Rx UEs 130. This is not limited in this embodiment ofthis application.

In an example, the Tx UE 110 may send the second multi-carrierconfiguration information by using a fifth message, where the fifthmessage may include but is not limited to an RRCReconfigurationSidelinkmessage on a PC5 interface or another new message that is not defined in3GPP TS.

In an example, the second multi-carrier configuration information mayinclude an identifier of at least one secondary carrier corresponding tothe Rx UE 130 in the plurality of secondary carriers, for example butnot limited to, a secondary carrier ID and a cell index. In addition,the second multi-carrier configuration information sent by the Tx UE 110to the Rx UE 130 may further include a parameter configuration of eachsecondary carrier, for example, a frequency band, a frequency, abandwidth, or a subcarrier spacing.

It should be noted that the Tx UE 110 may further perform setting basedon the first multi-carrier configuration information received from thenetwork device 120, to perform sidelink communication on the pluralityof secondary carriers. For example, the Tx UE 110 may add, based on theparameter configuration of each of the plurality of secondary carriers,each secondary carrier corresponding to each secondary carrieridentifier.

S310: One or more Rx UEs 130 send multi-carrier configuration completeindication information to the Tx UE 110, to indicate, to the Tx UE 110,that the multi-carrier configuration is completed.

For example, in S310 a, the Rx UE 130 a sends the multi-carrierconfiguration complete indication information to the Tx UE 110; and inS310 n, the Rx UE 130 n sends the multi-carrier configuration completeindication information to the Tx UE 110.

In an example, the one or more Rx UEs 130 may send the multi-carrierconfiguration complete indication information by using a sixth message,where the sixth message may include but is not limited to anRRCReconfigurationCompleteSidelink message on a PC5 interface or anothernew message that is not defined in 3GPP TS.

It should be noted that the Rx UE 130 may further perform setting basedon the second multi-carrier configuration information received from theTx UE 110, to perform sidelink communication on the at least onecorresponding secondary carrier. For example, the Rx UE 130 may add,based on the parameter configuration of each of the at least one ofsecondary carrier, each secondary carrier corresponding to eachsecondary carrier identifier.

S311: The Tx UE 110 sends the multi-carrier configuration completeindication information to the network device 120, to indicate, to thenetwork device 120, that the Tx UE 110 and the one or more Rx UEs 130have completed the multi-carrier configuration.

In an example, the Tx UE 110 may send the multi-carrier configurationcomplete indication information to the network device 120 by using aseventh message, where the seventh message may include anRRCConnectionReconfigurationComplete message defined in 3GPP TS 36.331or an RRCReconfigurationComplete message defined in 3GPP TS 38.331.Alternatively, the seventh message may include a new message that is notdefined in 3GPP TS.

In an example, the multi-carrier configuration complete indicationinformation may include identifiers of the one or more Rx UEs 130, toindicate, to the network device 120, Rx UEs 130 that each have completedthe multi-carrier configuration. The identifier of the Rx UE 130 mayinclude but is not limited to a destination layer-2 identifier(destination layer-2 ID) of the Rx UE 130, an index of the Rx UE 130,and the like. For example, the index of the Rx UE 130 may be an index ofeach Rx UE 130 included in the foregoing destination list indicationinformation, an index of each Rx UE 130 included in the foregoingmulti-carrier configuration request information, or an index of each RxUE 130 having established a sidelink connection to the Tx UE 110. Theindex of the Rx UE 130 is not specifically limited in this embodiment ofthis application.

S312: The Tx UE 110 sends, to the network device 120, information forrequesting resources required for data transmission.

In an example, the information for requesting resources required fordata transmission may include an SR and a BSR. The SR is used by the TxUE 110 to indicate, to the network device 120, that the Tx UE 110 hasdata to be transmitted, and the BSR is used by the Tx UE 110 toindicate, to the network device 120, an amount of data to be transmittedby the Tx UE 110.

S313: The network device 120 sends first secondary carrier statusindication information to the Tx UE 110.

The first secondary carrier status indication information may indicatean activated state or a deactivated state of at least one secondarycarrier corresponding to each of one or more Rx UEs 130. The one or moreRx UEs 130 may include but are not limited to the Rx UEs 130 that eachhave completed the multi-carrier configuration.

In an example, the network device 120 may send the first secondarycarrier status indication information to the Tx UE 110 based on a sizeof the data amount indicated in the BSR reported by the Tx UE 110.

In an example, the network device 120 may send the first secondarycarrier status indication information to the Tx UE 110 by using aneighth message, where the eighth message may include anRRCConnectionReconfiguration message defined in 3GPP TS 36.331, an RRCReconfiguration message defined in 3GPP TS 38.331, a medium accesscontrol (medium access control, MAC) control element (control element,CE) used to exchange MAC layer control information between the networkdevice 120 and the Tx UE 110, or a new message that is not defined in3GPP TS.

For example, the MAC CE used to exchange MAC layer control informationbetween the network device 120 and the Tx UE 110 may include a newlydefined sidelink SCell activation/deactivation MAC CE on a Uu interfacebetween the network device 120 and the Tx UE 110. In addition, whensending the MAC CE, the network device 120 further sends a MAC subheader(subheader) corresponding to the MAC CE. For a structure of the MACsubheader corresponding to the sidelink SCell activation/deactivationMAC CE on the Uu interface between the network device 120 and the Tx UE110, refer to the following descriptions of FIG. 4A and FIG. 4B. Itshould be noted that a value of an LCID field thereof is different froma value of an LCID field of a MAC subheader corresponding to a sidelinkSCell setup complete MAC CE used to indicate secondary carrier settingcomplete information.

It should be noted that a structure of the first secondary carrierstatus indication information is not limited in this embodiment of thisapplication. It addition, the network device 120 may further send, tothe Tx UE 110 through, for example, a PDCCH, information indicatingresources scheduled by the network device 120 for the Tx UE 110, wherethe resources are used by the Tx UE 110 to send data to the one or moreRx UEs 130 based on the radio bearer allocated by the network device120; and the network device 120 may perform resource scheduling based ona BSR reported by the Tx UE 110.

S314: The Tx UE 110 sends first acknowledgment information to thenetwork device 120, to indicate, to the network device 120, that thefirst secondary carrier status indication information is received fromthe network device 120.

It addition, the Tx UE 110 may further perform corresponding settingbased on the first secondary carrier status indication information. Thecorresponding setting may include: setting a lower layer to consideractivated states or deactivated states of the plurality of secondarycarriers, for example but not limited to, performing monitoring settingon a secondary carrier that is indicated to be in an activated state inthe first secondary carrier status indication information, and/orperforming de-monitoring setting on a secondary carrier that isindicated to be in a deactivated state in the first secondary carrierstatus indication information. For example, the lower layer may be aradio link control (radio link control, RLC) layer, a MAC layer, or aphysical (Physical, PHY) layer. The lower layer is not specificallylimited in this embodiment of this application.

S315: The Tx UE 110 separately sends second secondary carrier statusindication information to one or more Rx UEs 130. For example, in S315a, the Tx UE 110 may send the second secondary carrier status indicationinformation to the Rx UE 130 a; and in S315 n, the Tx UE 110 may sendthe second secondary carrier status indication information to the Rx UE130 n.

It can be understood that the Tx UE 110 may simultaneously orsequentially send the second secondary carrier status indicationinformation to the one or more Rx UEs 130. This is not limited in thisembodiment of this application.

The second secondary carrier status indication information may indicatean activated state or a deactivated state of a secondary carriercorresponding to each of the one or more Rx UEs 130. The one or more RxUEs 130 may include but are not limited to the Rx UEs 130 whosecorresponding secondary carriers are indicated to be in activated statesor deactivated states in the first secondary carrier status indicationinformation.

In an example, the Tx UE 110 may send the second secondary carrierstatus indication information by using a ninth message, where the ninthmessage may include an RRCReconfigurationSidelink message on a PC5interface, a MAC CE used to exchange a MAC layer control informationbetween the Tx UE 110 and the Rx UE 130, or another new message that isnot defined in 3GPP TS.

For example, the MAC CE used to exchange MAC layer control informationbetween the Tx UE 110 and the Rx UE 130 may include a newly definedsidelink SCell activation/deactivation MAC CE on the PC5 interface. Inaddition, when sending the MAC CE, the Tx UE 110 further sends a MACsubheader (subheader) corresponding to the MAC CE. For a structure ofthe MAC subheader corresponding to the sidelink SCellactivation/deactivation MAC CE on the PC5 interface, refer to thefollowing descriptions of FIG. 4A and FIG. 4B. It should be noted that avalue of an LCID field thereof is different from a value of an LCIDfield of a MAC subheader corresponding to a sidelink SCell setupcomplete MAC CE used to indicate secondary carrier setting completeinformation.

It should be noted that a structure of the second secondary carrierstatus indication information is not limited in this embodiment of thisapplication.

S316: One or more Rx UEs 130 that receive the second secondary carrierstatus indication information send second acknowledgment information tothe Tx UE 110, to indicate, to the Tx UE 110, that the one or more RxUEs 130 have received the second secondary carrier status indicationinformation from the Tx UE 110.

It should be noted that the one or more Rx UEs 130 that receive thesecond secondary carrier status indication information may also performcorresponding setting. The corresponding setting may include: setting alower layer to consider activated states or deactivated states ofcorresponding secondary carriers, for example but not limited to,performing monitoring setting on a corresponding secondary carrier thatis indicated to be in an activated state in the second secondary carrierstatus indication information, and/or performing de-monitoring settingon a corresponding secondary carrier that is indicated to be in adeactivated state in the second secondary carrier status indicationinformation. For example, the lower layer may be a radio link control(radio link control, RLC) layer, a MAC layer, or a physical (Physical,PHY) layer. The lower layer is not specifically limited in thisembodiment of this application.

S317: The Tx UE 110 sends secondary carrier setting complete informationto the network device 120 by using a tenth message, to indicate, to thenetwork device 120, that one or more Rx UEs 130 have completedcorresponding setting on corresponding secondary carriers in response tothe second secondary carrier status indication information.

In an example, the one or more Rx UEs 130 may include the Rx UEs 130from which the Tx UE 110 receives the second acknowledgment information.

In an example, the secondary carrier setting complete information may berelated to the numbers of the plurality of secondary carriers indicatedin the first multi-carrier configuration information. Details aredescribed in the following embodiment.

In an example, the tenth message may include a SidelinkUEInformationtype message, a UEAssistanceInformation message defined in 3GPP TS36.331 or 38.331, a medium access control (medium access control, MAC)control element (control element, CE) used to exchange MAC layer controlinformation between the network device 120 and the Tx UE 110, an uplinkcontrol information (uplink control information, UCI) message, or a newmessage that is not defined in 3GPP TS.

For example, the MAC CE may include a newly defined sidelink SCell setupcomplete MAC CE on a Uu interface between the network device 120 and theTx UE 110.

It should be noted that, when sending the MAC CE, the Tx UE 110 furthersends a MAC subheader (subheader) corresponding to the MAC CE, toindicate a type and a length of the MAC CE. FIG. 4A and FIG. 4B eachshow an example structure of the MAC subheader corresponding to thesidelink SCell setup complete MAC CE according to embodiments of thisapplication. As shown in FIG. 4A and FIG. 4B, the MAC subheadercorresponding to the sidelink SCell setup complete MAC CE mayspecifically include the following four fields:

R: Reserved bit.

F: 1 bit. The 1 bit is used to indicate a length of the L field. When avalue is 0, it indicates that the length of the L field is 8 bits; orwhen a value is 1, it indicates that a length of the L field is 16 bits.

LCID: 6 bits. A value of each bit is 0 or 1, and a value of the LCIDfield (which is not limited in this embodiment of this application) mayindicate that a MAC CE type field corresponding to the MAC subheader isthe sidelink SCell setup complete MAC CE from the Tx UE 110.

L: 8 bits or 16 bits. FIG. 4A shows a case in which the L field is 8bits, and FIG. 4B shows a case in which the L field is 16 bits. The Lfield is used to indicate a length of the sidelink SCell setup completeMAC CE corresponding to the MAC subheader. The length of the L field maybe indicated by the F field. In addition, when a length of the sidelinkSCell setup complete MAC CE on the Uu interface between the networkdevice 120 and the Tx UE 110 is a fixed value, the corresponding MACsubheader may not include the L field.

In an example, after the Tx UE 110 receives the second acknowledgmentinformation from the one or more Rx UEs 130, the Tx UE 110 directlysends the secondary carrier setting complete information to the networkdevice 120. In another example, after the Tx UE 110 receives the secondacknowledgment information from the one or more Rx UEs 130, the Tx UE110 waits for a preset time before sending the secondary carrier settingcomplete information to the network device 120. For example, the presettime may be 10 seconds, 30 seconds, or 1 minute. A specific value of thepreset time is not limited in this embodiment of this application. Thepreset time may be set in advance, or may be negotiated between the TxUE and the Rx UE.

It should be noted that an uplink resource is required for the Tx UE 110to send the tenth message to the network device 120. If the Tx UE 110currently has no available uplink resource, the Tx UE 110 further needsto request, from the network device 120, the uplink resource used tosend the tenth message, for example, send an SR to the network device120.

It should be noted that the Tx UE 110 may send the tenth message to thenetwork device 120 by using a reserved resource of the network device120. For example, when the network device 120 sends, to the Tx UE 110,the eighth message that is on the Uu interface and that is used by thenetwork device 120 to indicate the first secondary carrier statusindication information to the Tx UE 110, the network device 120 alsoreserves a resource location that corresponds to the eighth message andthat is used to send the tenth message, to ensure that the networkdevice 120 can distinguish the eighth message specifically correspondingto the tenth message sent by the Tx UE 110, that is, to ensure that thenetwork device 120 can learn of a setting status of the Rx UE 130 forthe secondary carrier.

It should be noted that the Tx UE 110 may alternatively send secondarycarrier setting incomplete information to the network device 120, toindicate, to the network device 120, that one or more Rx UEs 130 do notcomplete corresponding setting on corresponding secondary carriers inresponse to the second secondary carrier status indication information.In an example, the one or more Rx UEs 130 may include Rx UEs 130 fromwhich the Tx UE 110 does not receive the second acknowledgmentinformation.

It should be noted that a procedure of configuring a plurality ofcarriers between the Tx UE 110 and the network device 120 is not limitedto that shown in FIG. 3A to FIG. 3C. For example, the Tx UE 110 mayalternatively send the multi-carrier configuration request informationto the network device 120 in S301, and the network device 120 may sendthe first multi-carrier configuration information to the Tx UE 110 inS302.

The following uses five embodiments to describe in detail numberingperformed by the network device 120 and the Tx UE 110 on the secondarycarriers, and the secondary carrier setting complete information.

Embodiment 1

In this embodiment, the network device 120 performs local numbering onthe plurality of secondary carriers indicated in the first multi-carrierconfiguration information. The local numbering means that the networkdevice 120 separately performs numbering on the secondary carriers thatcorrespond to all the Rx UEs 130 and that are indicated in the firstmulti-carrier configuration information, and the secondary carrierscorresponding to all the Rx UEs 130 may have a same local number. Inthis case, the local numbers cannot uniquely determine the secondarycarriers of all the Rx UEs 130. Because the secondary carrier settingcomplete information is related to the local numbers of the secondarycarriers, the Tx UE 110 needs to add the identifiers of the Rx UEs 130to the secondary carrier setting complete information.

It should be noted that, in this embodiment, that the network device 120performs local numbering on the plurality of secondary carriersindicated in the first multi-carrier configuration information isrelated to S308 in FIG. 3A to FIG. 3C, and the secondary carrier settingcomplete information is related to S317 in FIG. 3A to FIG. 3C.

Local Numbering Performed by the Network Device 120 and the Tx UE 110 onthe Secondary Carriers

FIG. 5 shows an example of carrier allocation at the network device 120and an example of performing local numbering by the network device 120and the Tx UE 110 on the carriers. As shown in FIG. 5 , it is assumedthat the plurality of secondary carriers allocated to the Tx UE 110 atthe network device 120 include F₁, F₂, F₃, F₄, F₅, F₆, F₇, and F₅,Specifically, F₁, F₂, F₅, and F₈ are used by the Tx UE 110 to performsidelink communication with the Rx UE 130 a; F₃, F₆, and F₇ are used bythe Tx UE 110 to perform sidelink communication with the Rx UE 130 b;and F₁, F₄, F₆, and F₈ are used by the Tx UE 110 to perform sidelinkcommunication with the Rx UE 130 n.

In an example, the network device 120 may perform local numbering on theplurality of secondary carriers in an arrangement order of theidentifiers of the plurality of secondary carriers in the firstmulti-carrier configuration information. For example, assuming that anarrangement order of the secondary carriers corresponding to the Rx UE130 a in the first multi-carrier configuration information is F₁, F₂,F₅, and F₈, as shown in FIG. 5 , local numbers of the secondary carriersF₁, F₂, F₅, and F₈ at the network device 120 may be respectively“{circle around (1)}”, “{circle around (2)}”, “{circle around (3)}”, and“{circle around (4)}”; assuming that an arrangement order of thesecondary carriers corresponding to the Rx UE 130 b in the firstmulti-carrier configuration information is F₃, F₆, and F₇, as shown inFIG. 5 , local numbers of the secondary carriers F₃, F₆, and F₇ at thenetwork device 120 may be respectively “{circle around (1)}”, “{circlearound (2)}”, and “{circle around (3)}”; and assuming that anarrangement order of the secondary carriers corresponding to the Rx UE130 n in the first multi-carrier configuration information is F₁, F₂,F₆, and F₈, as shown in FIG. 5 , local numbers of the secondary carriersF₁, F₄, F₆, and F₈ at the network device 120 may be respectively“{circle around (1)}”, “{circle around (2)}”, “{circle around (3)}”, and“{circle around (4)}”.

In another example, the network device 120 may perform local numberingon the plurality of secondary carriers in a size arrangement order ofthe identifiers of the plurality of secondary carriers. For example,assuming that a size arrangement order of identifiers of the secondarycarriers corresponding to the Rx UE 130 a is F₁, F₂, F₆, and F₈, asshown in FIG. 5 , local numbers of F₁, F₂, F₅, and F₈ at the networkdevice 120 may be respectively “{circle around (1)}”, “{circle around(2)}”, “{circle around (3)}”, and “{circle around (4)}”: assuming that asize arrangement order of identifiers of the secondary carrierscorresponding to the Rx UE 130 b is F₃, F₆, and F₇, as shown in FIG. 5 ,local numbers of F₃, F₆, and F₇ at the network device 120 may berespectively “{circle around (1)}”, “{circle around (2)}”, and “{circlearound (3)}”; and assuming that a size arrangement order of identifiersof the secondary carriers corresponding to the Rx UE 130 n is F₁, F₄,F₆, and F₈, as shown in FIG. 5 , local numbers of F₁, F₄, F₆, and F₈ atthe network device 120 may be respectively “{circle around (1)}”,“{circle around (2)}”, “{circle around (3)}”, and “{circle around (4)}”.

It should be noted that carrier allocation at the network device 120 isnot limited to that shown in FIG. 5 , and the network device 120 mayalternatively perform local numbering on the plurality of secondarycarriers according to any other appropriate rule.

In addition, local numbering performed by the network device 120 on theplurality of secondary carriers may be used in S308 in FIG. 3A to FIG.3C, and the network device 120 may indicate the local numbers of theplurality of secondary carriers in the first multi-carrier configurationinformation. However, when there is a local numbering rule between theTx UE 110 and the network device 120 by default, the network device 120may alternatively not indicate the local numbers of the plurality ofsecondary carriers in the first multi-carrier configuration information.For example, the local numbering rule may be performing local numberingin the arrangement order of the identifiers of the plurality ofsecondary carriers in the first multi-carrier configuration informationor in the size arrangement order of the identifiers of the plurality ofsecondary carriers, for example, “{circle around (1)}”, “{circle around(2)}”, “{circle around (3)}”, and “{circle around (4)}”. The localnumbering rule is not limited in this embodiment of this application.

Secondary Carrier Setting Complete Information

When the secondary carrier setting complete information is used toindicate that only one Rx UE 130 has completed corresponding setting onat least one corresponding secondary carrier in response to the secondsecondary carrier status indication information, the first secondarycarrier status indication information may include a secondary carriersetting complete bitmap, and the secondary carrier setting completebitmap may include a first bitmap part and a second bitmap part. Thefirst bitmap part may be used to indicate an identifier of the Rx UE130, and the second bitmap part may be used to indicate that the Rx UE130 has completed the corresponding setting on the at least onecorresponding secondary carrier.

In an example, a type of the identifier of the Rx UE 130 used in thefirst bitmap part may be the same as or different from that of theidentifier of the Rx UE 130 used in the first multi-carrierconfiguration information.

In an example, at least one bit in the second bitmap part is in aone-to-one correspondence with the at least one secondary carriercorresponding to the Rx UE 130, and a value of each of the at least onebit may indicate that the Rx UE 130 has completed corresponding settingon a secondary carrier corresponding to the bit. For example, if a valueof a bit in the at least one bit is 0, it indicates that the Rx UE 130has completed corresponding setting for a deactivated state of acorresponding secondary carrier; or if a value of a bit in the at leastone bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, if a value of a bit in the atleast one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for a deactivated state of a correspondingsecondary carrier; or if a value of a bit in the at least one bit is 0,it indicates that the Rx UE 130 has completed corresponding setting foran activated state of a corresponding secondary carrier. For anotherexample, when a value of a bit in the at least one bit is 0 or 1, it mayindicate that the Rx UE 130 has completed corresponding setting on asecondary carrier corresponding to the bit (not specifically indicatewhether the corresponding setting is performed for an activated state ora deactivated state).

In an example, a total quantity of bits in the second bitmap part may berelated to one or more of the following: a maximum quantity of secondarycarriers supported by the Rx UE 130, a maximum quantity of secondarycarriers supported by the Tx UE 110, a quantity of secondary carrierscorresponding to the Rx UE 130, a maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110, and aquantity of available carriers at the network device 120. By way ofexample, and not limitation, when the maximum quantity of secondarycarriers supported by the Rx UE 130 is 8 and the maximum quantity ofsecondary carriers supported by the Tx UE 110 is 16, the total quantityof bits in the second bitmap part may be 8; when the maximum quantity ofsecondary carriers supported by the Rx UE 130 is 32 and the maximumquantity of secondary carriers supported by the Tx UE 110 is 16, thetotal quantity of bits in the second bitmap part may be 16: or when themaximum quantity of secondary carriers supported by each of the Rx UE130 and the Tx UE 110 is 16 and the maximum quantity of secondarycarriers that can be allocated by the network device 120 to the Tx UE110 is 8, the total quantity of bits in the second bitmap part may be 8.In addition, the total quantity of bits in the second bitmap part mayalternatively be a fixed quantity, and the fixed quantity is related toa maximum quantity of secondary carriers supported by all userequipments. By way of example, and not limitation, in all Tx UEs 110 andRx UEs 130, if a maximum quantity of supported secondary carriers is 32,the total quantity of bits in the second bitmap part may be 32.

In an example, the correspondence between the at least one bit in thesecond bitmap part and the at least one secondary carrier is related toa local number of the at least one secondary carrier at the networkdevice 120.

FIG. 6A to FIG. 8B each are a schematic diagram of a structure of thesecondary carrier setting complete information when the secondarycarrier setting complete information is used to indicate that only oneRx UE 130 has completed corresponding setting on at least onecorresponding secondary carrier. For each byte (Oct) shown in FIG. 6A toFIG. 8B, it is assumed that bits from right to left are arranged fromthe least significant bit to the most significant bit. In addition,SCell_(j) represents a secondary carrier whose local number is

where j is a positive integer.

In FIG. 6A, the first bitmap part in the secondary carrier settingcomplete information includes the four most significant bits in thefirst byte (Oct 1), to indicate an index of the Rx UE 130. Assuming thatthe total quantity of bits in the second bitmap part is 8, as shown inthe figure, the second bitmap part may include the four leastsignificant bits in the first byte (Oct 1) and the four most significantbits in the second byte (Oct 2). In addition, the i^(th) bit from rightto left in the four least significant bits in the first byte maycorrespond to a secondary carrier SCell_(i) (1≤i≤4), and the i^(th) bitfrom right to left in the four most significant bits in the second bytemay correspond to a secondary carrier SCell_(i) (5≤i≤8). It should benoted that a quantity of secondary carriers corresponding to the Rx UE130 may alternatively be less than 8. In this case, the second bitmappart includes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

FIG. 6B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that the Rx UE 130a in FIG. 5 has completed corresponding setting on the at least onecorresponding secondary carrier according to FIG. 6A As shown in thefigure, the first bitmap part in the secondary carrier setting completeinformation may include an index of the Rx UE 130 a. In 8 bits in thesecond bitmap part, the four least significant bits in the first byte(Oct 1) respectively correspond to the secondary carriers F₁, F₂, F₅,and F₅, Specifically, the least significant bit corresponds to thesecondary carrier F₁ (SCell_(i)) whose local number is “{circle around(1)}”, and a value of the bit is 1, indicating that the Rx UE 130 a hascompleted corresponding setting for an activated state of the secondarycarrier F₁; the second bit from right corresponds to the secondarycarrier F₂ (SCell₂) whose local number is “)”, and a value of the bit is0, indicating that the Rx UE 130 a has completed corresponding settingfor a deactivated state of the secondary carrier F₂; the third bit fromright corresponds to the secondary carrier F₈ (SCell₃) whose localnumber is “{circle around (3)}”, and a value of the bit is 1, indicatingthat the Rx LE 130 a has completed corresponding setting for anactivated state of the secondary carrier F₅; and the fourth bit fromright corresponds to the secondary carrier F₈ (SCell) whose local numberis “{circle around (4)}”, and a value of the bit is 0, indicating thatthe Rx UE 130 a has completed corresponding setting for a deactivatedstate of the secondary carrier F₅, The four most significant bits in thesecond byte in the second bitmap part do not correspond to any secondarycarrier, and values of the bits may be N.

In FIG. 6C, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 6A. Assuming that thetotal quantity of bits in the second bitmap part is 16, as shown in thefigure, the second bitmap part may include the four least significantbits in the first byte (Oct 1), the second byte (Oct 2), and the fourmost significant bits in the third byte (Oct 3). In addition, acorrespondence between the four least significant bits in the first byteand secondary carriers is the same as that in FIG. 6A, the i^(th) bitfrom right to left in the second byte may correspond to a secondarycarrier SCell_(i+4). (1≤i≤8), and the i^(th) bit from right to left inthe four most significant bits in the third byte may correspond to asecondary carrier SCell_(i+8) (5≤i≤8). It should be noted that aquantity of secondary carriers corresponding to the Rx UE 130 mayalternatively be less than 16. In this case, the second bitmap partincludes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

In FIG. 7A, the first bitmap part in the secondary carrier settingcomplete information includes the four least significant bits in thefirst byte (Oct 1), to indicate an index of the Rx UE 130. In addition,the four most significant bits in the first byte (Oct 1) are used asreserved bits R Assuming that the total quantity of bits in the secondbitmap part is 8, as shown in the figure, the second bitmap part mayinclude the second byte (Oct 2). In addition, the i^(th) bit from rightto left in the second byte (Oct 2) may correspond to a secondary carrierSCell_(i) (1≤i≤8). It should be noted that a quantity of secondarycarriers corresponding to the Rx UE 130 may alternatively be less than8. In this case, the second bitmap part includes bits that do notcorrespond to any secondary carrier, and values of these bits may be Nor values other than 0 and 1. Alternatively, in the first bitmap part,the four most significant bits in the first byte (Oct 1) may be used toindicate the index of the Rx UE 130, and the four least significant bitsmay be used as the reserved bits R.

In FIG. 7B, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 7A. Assuming that thetotal quantity of bits in the second bitmap part is 16, as shown in thefigure, the second bitmap part may include the second byte (Oct 2) andthe third byte (Oct 3). In addition, a correspondence between a bit inthe second byte and a secondary carrier is the same as that in FIG. 7A,and the i^(th) bit from right to left in the third byte may correspondto a secondary carrier SCell_(i+8) (1≤i≤8). It should be noted that aquantity of secondary carriers corresponding to the Rx UE 130 mayalternatively be less than 16. In this case, the second bitmap partincludes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

In FIG. 7C, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 7A. Assuming that thetotal quantity of bits in the second bitmap part is 8, as shown in thefigure, the second bitmap part may include the second byte (Oct 2). Inaddition, the least significant bit in the second byte (Oct 2) may beused as a reserved bit R. and the i^(th) bit from right to left maycorrespond to a secondary carrier SCell_(i−1) (2≤i≤8). It should benoted that a quantity of secondary carriers corresponding to the Rx UE130 may alternatively be less than 7. In this case, the second bitmappart includes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

In FIG. 8A, the first bitmap part in the secondary carrier settingcomplete information includes the first byte (Oct 1), the second byte(Oct 2), and the third byte (Oct 3), to indicate a destination layer-2identifier of the Rx UE 130. Assuming that the total quantity of bits inthe second bitmap part is 8, as shown in the figure, the second bitmappart may include the fourth byte (Oct 4). In addition, a correspondencebetween a bit in the fourth byte and a secondary carrier is the same asthat in FIG. 7A, and details are not described herein again. It shouldbe noted that a quantity of secondary carriers corresponding to the RxUE 130 may alternatively be less than 8. In this case, the second bitmappart includes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

In FIG. 8B, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 8A. Assuming that thetotal quantity of bits in the second bitmap part is 16, as shown in thefigure, the second bitmap part may include the fourth byte (Oct 4) andthe fifth byte (Oct 5). In addition, a correspondence between a bit inthe fourth byte and the fifth byte and a secondary carrier is the sameas that in FIG. 7B, and details are not described herein again. Itshould be noted that a quantity of secondary carriers corresponding tothe Rx UE 130 may alternatively be less than 16. In this case, thesecond bitmap part includes bits that do not correspond to any secondarycarrier, and values of these bits may be N or values other than 0 and 1.

It should be noted that the total quantity of bits in the first bitmappart and the total quantity of bits in second bitmap part in thesecondary carrier setting complete information are not limited to thoseshown in FIG. 6A to FIG. 8B. In addition, the correspondence between abit in the second bitmap part and a secondary carrier is not limited tothat shown in FIG. 6A to FIG. 8B either, provided that local numbers ofsecondary carriers corresponding to all bits from right to left (or fromleft to right) in each byte in the second bitmap part are arranged inorder of size.

It should be noted that, for each byte (Oct) shown in FIG. 6A to FIG.8B, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

When the secondary carrier setting complete information is used toindicate that a plurality of Rx UEs 130 have completed correspondingsetting on corresponding secondary carriers in response to the secondsecondary carrier status indication information, the secondary carriersetting complete information may include a secondary carrier settingcomplete bitmap, and the secondary carrier setting complete bitmap mayinclude a first bitmap part and a second bitmap part. The first bitmappart may be used to indicate an identifier of each of the plurality ofRx UEs 130, for example but not limited to, an index of each Rx UE 130or a destination layer-2 identifier of each Rx UE 130. The index of eachRx UE 130 may include but is not limited to an index of each Rx UE 130included in the foregoing destination list indication information, anindex of each Rx UE 130 included in the foregoing multi-carrierconfiguration request information, an index of each Rx UE 130 havingestablished a sidelink connection to the Tx UE 110, and the like. Thesecond bitmap part may be used to indicate that each of the plurality ofRx UEs 130 has completed corresponding setting on at least onecorresponding secondary carrier in response to the second secondarycarrier status indication information.

In an example, a total quantity of bits in the first bitmap part isrelated to a maximum quantity of Rx UEs supported by the Tx UE 110 (thatis, a maximum quantity of Rx UEs that simultaneously perform sidelinkcommunication with the Tx UE 110), a plurality of bits in the firstbitmap are in a one-to-one correspondence with the plurality of Rx UEs130, and the specific correspondence between the plurality of bits andthe plurality of Rx UEs 130 is related to the index of each of theplurality of Rx UEs 130. The index of each Rx UE 130 may include but isnot limited to an index of each Rx UE 130 included in the foregoingdestination list indication information, an index of each Rx UE 130included in the foregoing multi-carrier configuration requestinformation, an index of each Rx UE 130 having established a sidelinkconnection to the Tx UE 110, and the like.

In an example, the second bitmap part may include a plurality of bitrows corresponding to the plurality of Rx UEs 130. For example,quantities of bits included in all the bit rows may be the same or maybe different. For example, the bit row may include but is not limited toa byte. The bit row is not specifically limited in this embodiment ofthis application. Each of the plurality of Rx UEs 130 corresponds to atleast one bit row, the at least one bit row includes at least one bitthat is in a one-to-one correspondence with at least one secondarycarrier, a value of each bit indicates that the Rx UE 130 has completedcorresponding setting on a secondary carrier corresponding to the bit,and the at least one secondary carrier corresponds to the Rx UE 130. Forexample, if a value of a bit in the at least one bit is 0, it indicatesthat the Rx UE 130 has completed corresponding setting for a deactivatedstate of a corresponding secondary carrier: or if a value of a bit inthe at least one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, if a value of a bit in the atleast one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for a deactivated state of a correspondingsecondary carrier: or if a value of a bit in the at least one bit is 0,it indicates that the Rx UE 130 has completed corresponding setting foran activated state of a corresponding secondary carrier. For anotherexample, when a value of a bit in the at least one bit is 0 or 1, it mayindicate that the Rx UE 130 has completed corresponding setting on asecondary carrier corresponding to the bit (not specifically indicatewhether the corresponding setting is performed for an activated state ora deactivated state).

In addition, a total quantity of bits included in the at least one bitrow is related to one or more of the following: a maximum quantity ofsecondary carriers supported by the Rx UE 130 corresponding to the atleast one bit row, a maximum quantity of secondary carriers supported bythe Tx UE 110, a quantity of secondary carriers corresponding to the RxUE 130, a maximum quantity of secondary carriers that can be allocatedby the network device 120 to the Tx UE 110, and a quantity of availablecarriers at the network device 120. In addition, the total quantity ofbits in the at least one bit row may alternatively be a fixed quantity,and the fixed quantity is related to a maximum quantity of secondarycarriers supported by all user equipments (all Tx UEs 110 and Rx UEs130).

In addition, the correspondence between the at least one bit in the atleast one bit row and the at least one secondary carrier is related to alocal number of the at least one secondary carrier at the network device120.

FIG. 9A to FIG. 9D each are a schematic diagram of a structure of thesecondary carrier setting complete information when the secondarycarrier setting complete information is used to indicate that aplurality of Rx UEs 130 have completed corresponding setting oncorresponding secondary carriers in response to the second secondarycarrier status indication information. Each byte (Oct) shown in FIG. 9Ato FIG. 9D is equivalent to the foregoing one bit row. For each byte(Oct), it is assumed that bits from right to left are arranged from theleast significant bit to the most significant bit. In addition,SCell_(j) represents a secondary carrier whose local number is “{circlearound (j)}” at the network device 120, and Rx UE& represents Rx UE 130whose index is “k”, where j and k are positive integers.

In FIG. 9A, assuming that the maximum quantity of Rx UEs supported bythe Tx UE 110 is 16, the first bitmap part in the secondary carriersetting complete information may include the first byte (Oct 1) and thesecond byte (Oct 2). In addition, bits from right to left in the firstbyte sequentially correspond to Rx UE₁ to Rx UE₈, and bits from right toleft in the second byte sequentially correspond to Rx UE₉ to Rx UE₁₆. Inaddition, for each bit in the first bitmap part, when a value of the bitis 1, it may indicate that the secondary carrier setting completeinformation indicates a secondary carrier setting complete status of RxUE 130 corresponding to the bit: or when a value of the bit is 0, it mayindicate that the secondary carrier setting complete information doesnot indicate a secondary carrier setting complete status of Rx UE 130corresponding to the bit. In this case, the plurality of Rx UEs 130 area set of Rx UEs 130 corresponding to bits whose values are 1 in thefirst bitmap part. Alternatively, when a value of the bit is 0, it mayindicate that the secondary carrier setting complete informationindicates a secondary carrier setting complete status of Rx UE 130corresponding to the bit; or when a value of the bit is 1, it mayindicate that the secondary carrier setting complete information doesnot indicate a secondary carrier setting complete status of Rx UE 130corresponding to the bit. In this case, the plurality of Rx UEs 130 area set of Rx UEs 130 corresponding to bits whose values are 0 in thefirst bitmap part.

In FIG. 9A, assuming that a total quantity of bits included in at leastone bit row corresponding to each Rx UE 130 is 8, as shown in thefigure, in the second bitmap part in the secondary carrier settingcomplete information, each Rx UE 130 corresponds to one bit row (thatis, a byte). Specifically, the third byte (Oct 3) may correspond to RxUE 130 with the smallest index value in the plurality of Rx UEs 130,namely, Rx UE 130 corresponding to a bit when the first right-to-leftvalue from the first byte to the second byte in the first bitmap part is1, that is, when a value “1” of a bit indicates that the secondarycarrier setting complete information indicates a secondary carriersetting complete status of Rx UE 130 corresponding to the bit, or whenthe value is 0, that is, when a value “0” of a bit indicates that thesecondary carrier setting complete information indicates a secondarycarrier setting complete status of Rx UE 130 corresponding to the bit;and the fourth byte (Oct 4) may correspond to Rx UE 130 with the secondsmallest index value in the plurality of Rx UEs 130, namely, Rx UE 130corresponding to a bit when the second right-to-left value from thefirst byte to the second byte in the first bitmap part is 1, that is,when a value “1” of a bit indicates that the secondary carrier settingcomplete information indicates a secondary carrier setting completestatus of Rx UE 130 corresponding to the bit, or when the value is 0,that is, when a value “0” of a bit indicates that the secondary carriersetting complete information indicates a secondary carrier settingcomplete status of Rx UE 130 corresponding to the bit. By analogy, thetenth byte (Oct 10) may correspond to Rx UE 130 whose index value rankseighth (in ascending order) in the plurality of Rx UEs 130, namely, RxUE 130 corresponding to a bit when the eighth right-to-left value fromthe first byte to the second byte in the first bitmap part is 1, thatis, when a value “1” of a bit indicates that the secondary carriersetting complete information indicates a secondary carrier settingcomplete status of Rx UE 130 corresponding to the bit, or when the valueis 0, that is, when a value “0” of a bit indicates that the secondarycarrier setting complete information indicates a secondary carriersetting complete status of Rx UE 130 corresponding to the bit.

In addition, in the second bitmap part, for the byte corresponding toeach of the plurality of Rx UEs 130, the i^(th) bit from right to leftmay correspond to a secondary carrier SCell_(i) (1≤i≤8). It should benoted that a quantity of secondary carriers corresponding to each of theplurality of Rx UEs 130 may alternatively be less than 8. In this case,the byte corresponding to each Rx UE 130 includes bits that do notcorrespond to any secondary carrier, and values of these bits may be Nor values other than 0 and 1.

FIG. 9B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that the Rx UE 130a, the Rx UE 130 b, and the Rx UE 130 n in FIG. 5 have completedcorresponding setting on the corresponding secondary carriers accordingto FIG. 9A. It is assumed that an index of the Rx UE 130 a is 1, anindex of the Rx UE 130 b is 4, and an index of the Rx UE 130 n is 9. Inthis case, as shown in FIG. 9B, in the first bitmap part, values of thefirst bit and the fourth bit from right to left in the first byte(Oct 1) and the first bit from right to left in the second byte (Oct 2)are 1, and values of the other bits are 0; and the second bitmap partincludes the third byte (Oct 3), the fourth byte (Oct 4), and the fifthbyte (Oct 5). Bits in the third byte may respectively correspond to thesecondary carriers F₁, F₂, F₅, and F₈ corresponding to the Rx UE 130 a.Specifically, the least significant bit corresponds to the secondarycarrier F₁ (SCell₁) whose local number is “W”, and a value of the bit is1, indicating that the Rx UE 130 a has completed corresponding settingfor an activated state of the secondary carrier F₁; the second bit fromright corresponds to the secondary carrier F₂ (SCell₂) whose localnumber is “{circle around (2)}”, and a value of the bit is 0, indicatingthat the Rx UE 130 a has completed corresponding setting for adeactivated state of the secondary carrier F₂: the third bit from rightcorresponds to the secondary carrier F₈ (SCell₃) whose local number is“0”, and a value of the bit is 1, indicating that the Rx UE 130 a hascompleted corresponding setting for an activated state of the secondarycarrier F₅; the fourth bit from right corresponds to the secondarycarrier F₈ (SCell₄) whose local number is “{circle around (4)}”, and avalue of the bit is 0, indicating that the Rx UE 130 a has completedcorresponding setting for a deactivated state of the secondary carrierFR; and the other bits do not correspond to any secondary carrier, andvalues of the bits may be N. Bits in the fourth byte may respectivelycorrespond to the secondary carriers F₃, F₆, and F₇ corresponding to theRx UE 130 b. Specifically, the least significant bit corresponds to thesecondary carrier F₃ (SCell₁) whose local number is “{circle around(1)}”, and a value of the bit is 0, indicating that the Rx UE 130 b hascompleted corresponding setting for a deactivated state of the secondarycarrier F₃; the second bit from right corresponds to the secondarycarrier F₆ (SCell₂) whose local number is “)”, and a value of the bit is1, indicating that the Rx UE 130 b has completed corresponding settingfor a deactivated state of the secondary carrier F₆; the third bit fromright corresponds to the secondary carrier F₇(SCell₃) whose local numberis “{circle around (3)}”, and a value of the bit is 1, indicating thatthe Rx UE 130 b has completed corresponding setting for an activatedstate of the secondary carrier F₇; and the other bits do not correspondto any secondary carrier, and values of the bits may be N. Bits in thefifth byte may respectively correspond to the secondary carriers F₁, F₄,F₆, and F₈ corresponding to the Rx UE 130 n. Specifically, the leastsignificant bit corresponds to the secondary carrier F₁ (SCell₁) whoselocal number is “{circle around (1)}”, and a value of the bit is 1,indicating that the Rx UE 130 n has completed corresponding setting foran activated state of the secondary carrier F₁; the second bit fromright corresponds to the secondary carrier F₄ (SCell₂) whose localnumber is “{circle around (2)}”, and a value of the bit is 1, indicatingthat the Rx UE 130 n has completed corresponding setting for anactivated state of the secondary carrier F₄; the third bit from rightcorresponds to the secondary carrier F₆ (SCell₃) whose local number is“{circle around (3)}”, and a value of the bit is 0, indicating that theRx UE 130 n has completed corresponding setting for a deactivated stateof the secondary carrier F₆; the fourth bit from right corresponds tothe secondary carrier F₈ (SCell) whose local number is “{circle around(4)}”, and a value of the bit is 0, indicating that the Rx UE 130 n hascompleted corresponding setting for a deactivated state of the secondarycarrier F₈; and the other bits do not correspond to any secondarycarrier, and values of the bits may be N.

In FIG. 9C, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 9A. Assuming that atotal quantity of bits included in at least one bit row corresponding toeach Rx UE 130 is 16, as shown in the figure, in the second bitmap part,each Rx UE 130 corresponds to two bit rows (that is, bytes).Specifically, the third byte (Oct 3) and the fourth byte (Oct 4) maycorrespond to Rx UE 130 with the smallest index value in the pluralityof Rx UEs 130, namely, Rx UE 130 corresponding to a bit when the firstright-to-left value from the first byte to the second byte in the firstbitmap part is 1, that is, when a value “1” of a bit indicates that thesecondary carrier setting complete information indicates a secondarycarrier setting complete status of Rx UE 130 corresponding to the bit,or when the value is 0, that is, when a value “0” of a bit indicatesthat the secondary carrier setting complete information indicates asecondary carrier setting complete status of Rx UE 130 corresponding tothe bit; and the fifth byte (Oct 5) and the sixth byte (Oct 6) maycorrespond to Rx UE 130 with the second smallest index value in theplurality of Rx UEs 130, namely, Rx UE 130 corresponding to a bit whenthe second right-to-left value from the first byte to the second byte inthe first bitmap part is 1, that is, when a value “1” of a bit indicatesthat the secondary carrier setting complete information indicates asecondary carrier setting complete status of Rx UE 130 corresponding tothe bit, or when the value is 0, that is, when a value “0” of a bitindicates that the secondary carrier setting complete informationindicates a secondary carrier setting complete status of Rx UE 130corresponding to the bit. By analogy, the ninth byte (Oct 9) and thetenth byte (Oct 10) may correspond to Rx UE 130 whose index value ranksfourth (in ascending order) in the plurality of Rx UEs 130, namely, RxUE 130 corresponding to a bit when the fourth right-to-left value fromthe first byte to the second byte in the first bitmap part is 1, thatis, when a value “1” of a bit indicates that the secondary carriersetting complete information indicates a secondary carrier settingcomplete status of Rx UE 130 corresponding to the bit, or when the valueis 0, that is, when a value “0” of a bit indicates that the secondarycarrier setting complete information indicates a secondary carriersetting complete status of Rx UE 130 corresponding to the bit.

In addition, in the second bitmap part, for the two bytes correspondingto each of the plurality of Rx UEs 130, a correspondence between a bitin one byte and a secondary carrier is the same as that in FIG. 9A, andthe i^(th) bit from right to left in the other byte may correspond to asecondary carrier SCell₁₊₈ (1≤i≤8). It should be noted that a quantityof secondary carriers corresponding to each Rx UE 130 may alternativelybe less than 16. In this case, the two bytes corresponding to each Rx UE130 include bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

In FIG. 9D, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 9A, and a specificcorrespondence between each Rx UE 130 and a bit row (that is, a byte) inthe second bitmap part is also the same as that in FIG. 9A. For the bytecorresponding to each Rx UE 130, the least significant bit may be usedas a reserved bit R, and the i^(th) bit from right to left maycorrespond to a secondary carrier SCell_(i−1) (2≤i≤8). It should benoted that a quantity of secondary carriers corresponding to each Rx UE130 may alternatively be less than 7. In this case, the bytecorresponding to each Rx UE 130 includes bits that do not correspond toany secondary carrier, and values of these bits may be N or values otherthan 0 and 1.

It should be noted that the total quantity of bits in the first bitmappart and the total quantity of bits in the at least one bit rowcorresponding to each Rx UE 130 in the second bitmap part are notlimited to those shown in FIG. 9A to FIG. 9D. In addition, thecorrespondence between a bit in the at least one bit row correspondingto each Rx UE 130 in the second bitmap part and a secondary carrier isnot limited to that shown in FIG. 9A to FIG. 9D either, provided thatlocal numbers of secondary carriers corresponding to all bits from rightto left (or from left to right) in each bit row (or each byte) arearranged in order of size.

It should be noted that, for each byte (Oct) shown in FIG. 9A to FIG.9D, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

In another example, the first bitmap part may include indexes ordestination layer-2 identifiers of the plurality of Rx UEs 130. Forexample, the index of each of the plurality of Rx UEs 130 may be anindex of each Rx UE 130 included in the foregoing destination listindication information, an index of each Rx UE 130 included in theforegoing multi-carrier configuration request information, or an indexof each Rx UE 130 having established a sidelink connection to the Tx UE110. The index of each of the plurality of Rx UEs 130 is notspecifically limited in this embodiment of this application. The secondbitmap part may include a plurality of subparts that are in a one-to-onecorrespondence with the plurality of Rx UEs 130, each subpart includesat least one bit, the at least one bit is in a one-to-one correspondencewith at least one secondary carrier, a value of each of the at least onebit may indicate that Rx UE 130 corresponding to the subpart hascompleted corresponding setting on a secondary carrier corresponding tothe bit, and the at least one secondary carrier corresponds to the Rx UE130. For example, if a value of a bit in the at least one bit is 0, itindicates that the Rx UE 130 has completed corresponding setting for adeactivated state of a corresponding secondary carrier; or if a value ofa bit in the at least one bit is 1, it indicates that the Rx UE 130 hascompleted corresponding setting for an activated state of acorresponding secondary carrier. For another example, if a value of abit in the at least one bit is 1, it indicates that the Rx UE 130 hascompleted corresponding setting for a deactivated state of acorresponding secondary carrier; or if a value of a bit in the at leastone bit is 0, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, when a value of a bit in the atleast one bit is 0 or 1, it may indicate that the Rx UE 130 hascompleted corresponding setting on a secondary carrier corresponding tothe bit (not specifically indicate whether the corresponding setting isperformed for an activated state or a deactivated state).

In addition, in the second bitmap part, for each of the plurality of RxUEs 130, the correspondence between the at least one bit and the atleast one secondary carrier is related to a local number of the at leastone secondary carrier at the network device 120.

In addition, a total quantity of bits included in each subpart in thesecond bitmap part may be related to one or more of the following: amaximum quantity of secondary carriers supported by the Rx UE 130corresponding to the subpart, a maximum quantity of secondary carrierssupported by the Tx UE 110, a quantity of secondary carrierscorresponding to the Rx UE 110, a maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110, and aquantity of available carriers at the network device 120. In addition,the total quantity of bits included in the at least one bit row mayalternatively be a fixed quantity, and the fixed quantity is related toa maximum quantity of secondary carriers supported by all userequipments (all Tx UEs 110 and Rx UEs 130).

FIG. 10A to FIG. 12B each are a schematic diagram of a structure of thesecondary carrier setting complete information when the secondarycarrier setting complete information is used to indicate that aplurality of Rx UEs 130 have completed corresponding setting oncorresponding secondary carriers in response to the second secondarycarrier status indication information. It is assumed that bits fromright to left are arranged from the least significant bit to the mostsignificant bit. In addition, SCell_(j) represents a secondary carrierwhose local number is

at the network device 120.

In FIG. 10A, assuming that a total quantity of bits included in asubpart corresponding to each Rx UE 130 is 8, the four most significantbits in the first byte (Oct 1) may be used to indicate an index of thefirst Rx UE 130 (Rx UE₁) in the plurality of Rx UEs 130, the four leastsignificant bits in the first byte (Oct 1) and the four most significantbits in the second byte (Oct 2) are a subpart corresponding to the RxUE₁ in the second bitmap part, the i^(th) bit from right to left in thefour least significant bits in the first byte (Oct 1) may correspond toa secondary carrier SCell_(i) (1≤i≤4), and the i^(th) bit from right toleft in the four most significant bits in the second byte (Oct 2) maycorrespond to a secondary carrier SCell_(i) (5≤i≤8); the four leastsignificant bits in the second byte (Oct 2) may be used to indicate anindex of the second Rx UE 130 (Rx UE₂) in the plurality of Rx UEs 130,the third byte (Oct 3) is a subpart corresponding to the Rx UE₂ in thesecond bitmap part, and the i^(th) bit from right to left in the thirdbyte (Oct 3) may correspond to a secondary carrier SCell_(i) (1≤i≤8);the four most significant bits in the fourth byte (Oct 4) may be used toindicate an index of the third Rx UE 130 (Rx UE₃) in the plurality of RxUEs 130, the four least significant bits in the fourth byte (Oct 4) andthe four most significant bits in the fifth byte (Oct 5) may be asubpart corresponding to the Rx UEs in the second bitmap part, thei^(th) bit from right to left in the four least significant bits in thefourth byte (Oct 4) may correspond to a secondary carrier SCell;(1≤i≤4), and the i^(th) bit from right to left in the four mostsignificant bits in the fifth byte (Oct 5) may correspond to a secondarycarrier SCell_(i) (5≤i≤8); and so on, until the last Rx UE 130 in theplurality of Rx UEs 130. It should be noted that a quantity of secondarycarriers corresponding to each of the plurality of Rx UEs 130 mayalternatively be less than 8. In this case, the byte corresponding toeach Rx UE 130 includes bits that do not correspond to any secondarycarrier, and values of these bits may be N or values other than 0 and 1.

In addition, in FIG. 10A, the first bitmap part may include the fourmost significant bits in the first byte (Oct 1), the four leastsignificant bits in the second byte (Oct 2), the four most significantbits in the fourth byte (Oct 4), and the like.

In FIG. 10B, assuming that a total quantity of bits included in asubpart corresponding to each Rx UE 130 is 16, the four most significantbits in the first byte (Oct 1) may be used to indicate an index of thefirst Rx UE 130 (Rx UE₁) in the plurality of Rx UEs 130, the four leastsignificant bits in the first byte (Oct 1), the second byte (Oct 2), andthe four most significant bits in the third byte (Oct 3) may be asubpart corresponding to the Rx UE₁ in the second bitmap part, thei^(th) bit from right to left in the four least significant bits in thefirst byte (Oct 1) may correspond to a secondary carrier SCell_(i)(1≤i≤4), the i^(th) bit from right to left in the second byte (Oct 2)may correspond to a secondary carrier SCell_(i+4) (1≤i≤8), and thei^(th) bit from right to left in the four most significant bits in thethird byte (Oct 3) may correspond to a secondary carrier SCell_(i+8)(5≤i≤8); the four least significant bits in the third byte (Oct 3) maybe used to indicate an index of the second Rx UE 130 (Rx UE₂) in theplurality of Rx UEs 130, the fourth byte (Oct 4) and the fifth byte (Oct5) are a subpart corresponding to the Rx UE₂ in the second bitmap part,the i^(th) bit from right to left in the fourth byte (Oct 4) maycorrespond to a secondary carrier SCell; (1≤i≤8), and the i^(th) bitfrom right to left in the fifth byte (Oct 5) may correspond to asecondary carrier SCell_(i+8) (1≤i≤8); and so on, until the last Rx UE130 in the plurality of Rx UEs 130. It should be noted that a quantityof secondary carriers corresponding to each of the plurality of Rx UEs130 may alternatively be less than 16. In this case, the bytecorresponding to each Rx UE 130 includes bits that do not correspond toany secondary carrier, and values of these bits may be N or values otherthan 0 and 1.

In addition, in FIG. 10B, the first bitmap part may include the fourmost significant bits in the first byte (Oct 1), the four leastsignificant bits in the third byte (Oct 3), and the like.

In FIG. 11A, assuming that a total quantity of bits included in asubpart corresponding to each Rx UE 130 is 8, the four least significantbits in the first byte (Oct 1) may be used to indicate an index of thefirst Rx UE 130 (Rx UE₁) in the plurality of Rx UEs 130, the four mostsignificant bits in the first byte (Oct 1) may be used as reserved bitsR, the second byte (Oct 2) may be a subpart corresponding to the Rx UE₁in the second bitmap part, and the i^(th) bit from right to left in thesecond byte (Oct 2) may correspond to a secondary carrier SCell_(i)(1≤i≤8): the four least significant bits in the third byte (Oct 3) maybe used to indicate an index of the second Rx UE 130 (Rx UE₂) in theplurality of Rx UEs 130, the four most significant bits in the thirdbyte (Oct 3) may be used as reserved bits R, the fourth byte (Oct 4) isa subpart corresponding to the Rx UE₂ in the second bitmap part, acorrespondence between each bit in the fourth byte and a secondarycarrier is similar to a correspondence with the Rx UE₁, and details arenot described herein again; the four least significant bits in the fifthbyte (Oct 5) may be used to indicate an index of the third Rx UE 130 (RxUE₂) in the plurality of Rx UEs 130, the four most significant bits inthe fifth byte (Oct 5) may be used as reserved bits R, the sixth byte(Oct 6) is a subpart corresponding to the Rx UE₃ in the second bitmappart, a correspondence between each bit in the sixth byte and asecondary carrier is similar to a correspondence with the Rx UE₁, anddetails are not described herein again; and so on, until the last Rx UE130 in the plurality of Rx UEs 130. It should be noted that a quantityof secondary carriers corresponding to each of the plurality of Rx UEs130 may alternatively be less than 8. In this case, the bytecorresponding to each Rx UE 130 includes bits that do not correspond toany secondary carrier, and values of these bits may be N or values otherthan 0 and 1. Alternatively, the foregoing bits used to indicate theindex of the Rx UE 130 may be used as the reserved bits R, and theforegoing reserved bits R may be used to indicate the index of the Rx UE130.

In addition, in FIG. 11A, the first bitmap part may include the fourleast significant bits in the first byte (Oct 1), the four leastsignificant bits in the third byte (Oct 3), the four least significantbits in the fifth byte (Oct 5), and the like.

In FIG. 11B, assuming that a total quantity of bits included in asubpart corresponding to each Rx UE 130 is 16, the four leastsignificant bits in the first byte (Oct 1) may be used to indicate anindex of the first Rx UE 130 (Rx UE₁) in the plurality of Rx UEs 130,the four most significant bits in the first byte (Oct 1) may be used asreserved bits R, the second byte (Oct 2) and the third byte (Oct 3) area subpart corresponding to the Rx UE₁ in the second bitmap part, thei^(th) bit from right to left in the second byte (Oct 2) may correspondto a secondary carrier SCell_(i) (1≤i≤8), and the i^(th) bit from rightto left in the third byte (Oct 3) may correspond to a secondary carrierSCell_(i+8) (1≤i≤8); the four least significant bits in the fourth byte(Oct 4) may be used to indicate an index of the second Rx UE 130 (RxUE₂) in the plurality of Rx UEs 130, the four most significant bits inthe fourth byte (Oct 4) may be used as reserved bits R, the fifth byte(Oct 5) and the sixth byte (Oct 6) are a subpart corresponding to the RxUE₂ in the second bitmap part, a correspondence between each bit in thefifth byte and the sixth byte and a secondary carrier is similar to acorrespondence with the Rx UE₁, and details are not described hereinagain; the four least significant bits in the seventh byte (Oct 7) maybe used to indicate an index of the third Rx UE 130 (Rx UE₃) in theplurality of Rx UEs 130, the four most significant bits in the seventhbyte (Oct 7) may be used as reserved bits R, the eighth byte (Oct 8) andthe ninth byte (Oct 9) are a subpart corresponding to the Rx UE₃ in thesecond bitmap part, a correspondence between each bit in the eighth byteand the ninth byte and a secondary carrier is similar to acorrespondence with the Rx UE₁, and details are not described hereinagain; and so on, until the last Rx UE 130 in the plurality of Rx UEs130. It should be noted that a quantity of secondary carrierscorresponding to each of the plurality of Rx UEs 130 may alternativelybe less than 16. In this case, the byte corresponding to each Rx UE 130includes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.Alternatively, the foregoing bits used to indicate the index of the RxUE 130 may be used as the reserved bits R, and the foregoing reservedbits R may be used to indicate the index of the Rx UE 130.

In addition, in FIG. 1B, the first bitmap part may include the fourleast significant bits in the first byte (Oct 1), the four leastsignificant bits in the fourth byte (Oct 4), the four least significantbits in the seventh byte (Oct 7), and the like.

In FIG. 12A, assuming that a total quantity of bits included in asubpart corresponding to each Rx UE 130 is 8, the first byte (Oct 1) tothe third byte (Oct 3) may be used to indicate a destination layer-2identifier of the first Rx UE 130 (Rx UE₁) in the plurality of Rx UEs130, the fourth byte (Oct 4) is a subpart corresponding to the Rx UE, inthe second bitmap part, and the i^(th) bit from right to left in thefourth byte (Oct 4) may correspond to a secondary carrier SCell;(1≤i≤8); the fifth byte (Oct 5) to the seventh byte (Oct 7) may be usedto indicate a destination layer-2 identifier of the second Rx UE 130 (RxUE₂) in the plurality of Rx UEs 130, the eighth byte (Oct 8) is asubpart corresponding to the Rx UE₂ in the second bitmap part, acorrespondence between each bit in the eight byte and a secondarycarrier is similar to a correspondence with the Rx UE₁, and details arenot described herein again; and so on, until the last Rx UE 130 in theplurality of Rx UEs 130. It should be noted that a quantity of secondarycarriers corresponding to each of the plurality of Rx UEs 130 mayalternatively be less than 8. In this case, the byte corresponding toeach Rx UE 130 includes bits that do not correspond to any secondarycarrier, and values of these bits may be N or values other than 0 and 1.

In addition, in FIG. 12A, the first bitmap part may include the firstbyte (Oct 1) to the third byte (Oct 3), the fifth byte (Oct 5) to theseventh byte (Oct 7), and the like.

In FIG. 12B, assuming that a total quantity of bits included in asubpart corresponding to each Rx UE 130 is 16, the first byte (Oct 1) tothe third byte (Oct 3) may be used to indicate a destination layer-2identifier of the first Rx UE 130 (Rx UE₁) in the plurality of Rx UEs130, the fourth byte (Oct 4) and the fifth byte (Oct 5) are a subpartcorresponding to the Rx UE₁ in the second bitmap part, the i^(th) bitfrom right to left in the fourth byte (Oct 4) may correspond to asecondary carrier SCell_(i)(1≤i≤8), and the i^(th) bit from right toleft in the fifth byte (Oct 5) may correspond to a secondary carrierSCell_(i+8) (1≤i≤8); the sixth byte (Oct 6) to the eighth byte (Oct 8)may be used to indicate a destination layer-2 identifier of the secondRx UE 130 (Rx UE₂) in the plurality of Rx UEs 130, the ninth byte (Oct9) and the tenth byte (Oct 10) are a subpart corresponding to the Rx UE₂in the second bitmap part, a correspondence between each bit in theninth byte and the tenth byte and a secondary carrier is similar to acorrespondence with the Rx UE₁, and details are not described hereinagain; and so on, until the last Rx UE 130 in the plurality of Rx UEs130. It should be noted that a quantity of secondary carrierscorresponding to each of the plurality of Rx UEs 130 may alternativelybe less than 16. In this case, the byte corresponding to each Rx UE 130includes bits that do not correspond to any secondary carrier, andvalues of these bits may be N or values other than 0 and 1.

In addition, in FIG. 12B, the first bitmap part may include the firstbyte (Oct 1) to the third byte (Oct 3), the sixth byte (Oct 6) to theeighth byte (Oct 8), and the like.

It should be noted that, in the first bitmap part in the secondarycarrier setting complete information, the identifier of each of theplurality of Rx UEs 130 may occupy any quantity of bits, and thequantity is not limited to that shown in FIG. 10A to FIG. 12B; and inthe second bitmap part, the total quantity of bits in each subpartcorresponding to each of the plurality of Rx UEs 130 is not limited tothat shown in FIG. 10A to FIG. 12B either. In addition, thecorrespondence between each bit in each subpart and a secondary carrieris not limited to that shown in FIG. 10A to FIG. 12B either, providedthat local numbers of secondary carriers corresponding to all bits fromright to left (or from left to right) are arranged in order of size.

It should be noted that, for each byte (Oct) shown in FIG. 10A to FIG.12B, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

It should be noted that the secondary carrier setting completeinformation having the foregoing structure in this embodiment may beused in S317 in FIG. 3A to FIG. 3C.

Embodiment 2

In this embodiment, the network device 120 performs globally uniquenumbering on the plurality of secondary carriers indicated in the firstmulti-carrier configuration information. The globally unique numberingmeans that the network device 120 performs global numbering on theplurality of secondary carriers or available carriers at the networkdevice 120, and each of the plurality of secondary carriers has only onenumber. In this case, because the network device 120 may configure asame secondary carrier for sidelink communication between the Tx UE 110and different Rx UEs 130, Rx UE 130 corresponding to a secondary carriercannot be determined based on a globally unique number of the secondarycarrier. Therefore, the Tx UE 110 needs to add an identifier of the RxUE 130 to the secondary carrier setting complete information.

It should be noted that, in this embodiment, that the network device 120performs globally unique numbering on the plurality of secondarycarriers indicated in the first multi-carrier configuration informationis related to S308 in FIG. 3A to FIG. 3C, and the secondary carriersetting complete information is related to S317 in FIG. 3A to FIG. 3C.

Numbering Performed by the Network Device 120 and the Tx UE 110 on theSecondary Carriers

FIG. 13 shows an example of carrier allocation at the network device 120and an example of performing globally unique numbering by the networkdevice 120 on the carriers and performing local numbering by the Tx UE110 on the carriers. As shown in FIG. 13 , it is assumed that theplurality of secondary carriers allocated to the Tx UE 110 at thenetwork device 120 include F₁, F₂, F₃, F₄, F₅, F₆, F₇, and F₈.Specifically, F₁, F₂, F₃, and F₈ are used by the Tx UE 110 to performsidelink communication with the Rx UE 130 a; F₃, F₆, and F₇ are used bythe Tx UE 110 to perform sidelink communication with the Rx UE 130 b;and F₁, F₄, F₆, and F₈ are used by the Tx UE 110 to perform sidelinkcommunication with the Rx UE 130 n.

In an example, the network device 120 may perform globally uniquenumbering in an arrangement order of the identifiers of the plurality ofsecondary carriers in the first multi-carrier configuration information.For example, assuming that the arrangement order of the secondarycarriers in the first multi-carrier configuration information is F₁, F₂,F₃, F₄, F₅, F₆, F₇, and F₈, as shown in FIG. 18 , globally uniquenumbers of the secondary carriers F₁ to F₈ at the network device 120 maybe respectively “{circle around (1)}”, “{circle around (2)}”, “{circlearound (3)}”, “{circle around (4)}”, “{circle around (5)}”, “{circlearound (6)}”, “{circle around (7)}”, and “{circle around (8)}”.

In another example, the network device 120 may perform globally uniquenumbering in a size arrangement order of the identifiers of theplurality of secondary carriers or the available carriers at the networkdevice 120. For example, assuming that the arrangement order of thesecondary carriers in ascending order is F₁, F₂, F₃, F₄, F₅, F₆, F₇, andF₈, as shown in FIG. 18 , globally unique numbers of the secondarycarriers F₁ to F₈ at the network device 120 may be respectively “{circlearound (1)}”, “{circle around (2)}”, “{circle around (3)}”, “{circlearound (4)}”, “{circle around (5)}”, “{circle around (6)}”, “{circlearound (7)}”, and “{circle around (8)}”.

It should be noted that carrier allocation at the network device 120 isnot limited to that shown in FIG. 13 , and the network device 120 mayalternatively perform globally unique numbering on the plurality ofsecondary carriers according to any other appropriate rule.

In addition, local numbering performed by the network device 120 on theplurality of secondary carriers may be used in S308 in FIG. 3A to FIG.3C, and the network device 120 may indicate the globally unique numbersof the plurality of secondary carriers in the first multi-carrierconfiguration information. However, when there is a globally uniquenumbering rule between the Tx UE 110 and the network device 120 bydefault, the network device 120 may alternatively not indicate theglobally unique numbers of the plurality of secondary carriers in thefirst multi-carrier configuration information. For example, the globallyunique numbering rule may be performing numbering in the arrangementorder of the identifiers of the plurality of secondary carriers in thefirst multi-carrier configuration information or in the size arrangementorder of the identifiers of the available carriers at the network device120, for example, “{circle around (1)}”, “{circle around (2)}”, “{circlearound (3)}”, “{circle around (4)}”, “{circle around (5)}”, “{circlearound (6)}”, “{circle around (7)}”, and “{circle around (8)}”. Theglobally unique numbering rule is not limited in this embodiment of thisapplication.

Secondary Carrier Setting Complete Information

When the secondary carrier setting complete information is used toindicate that only one Rx UE 130 has completed corresponding setting onat least one corresponding secondary carrier in response to the secondsecondary carrier status indication information, the secondary carriersetting complete information may include a secondary carrier settingcomplete bitmap, and the secondary carrier setting complete bitmap mayinclude a first bitmap part and a second bitmap part. The first bitmappart may be used to indicate an identifier of the Rx UE 130, and thesecond bitmap part may be used to indicate that the Rx UE 130 hascompleted the corresponding setting on the at least one correspondingsecondary carrier.

In an example, a type of the identifier of the Rx UE 130 used in thefirst bitmap part may be the same as or different from that of theidentifier of the Rx UE 130 used in the first multi-carrierconfiguration information.

In an example, at least one bit in the second bitmap part is in aone-to-one correspondence with the at least one secondary carriercorresponding to the Rx UE 130, and a value of each of the at least onebit may indicate that the Rx UE 130 has completed corresponding settingon a secondary carrier corresponding to the bit. For example, if a valueof a bit in the at least one bit is 0, it indicates that the Rx UE 130has completed corresponding setting for a deactivated state of acorresponding secondary carrier; or if a value of a bit in the at leastone bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, if a value of a bit in the atleast one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for a deactivated state of a correspondingsecondary carrier; or if a value of a bit in the at least one bit is 0,it indicates that the Rx UE 130 has completed corresponding setting foran activated state of a corresponding secondary carrier. For anotherexample, when a value of a bit in the at least one bit is 0 or 1, it mayindicate that the Rx UE 130 has completed corresponding setting on asecondary carrier corresponding to the bit (not specifically indicatewhether the corresponding setting is performed for an activated state ora deactivated state).

In an example, a total quantity of bits in the second bitmap part may berelated to a maximum quantity of secondary carriers that can beallocated by the network device 120 to the Tx UE 110 or a quantity ofavailable carriers at the network device 120. For example, when themaximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 8, the total quantity of bits inthe second bitmap part may be 8; or when the maximum quantity ofsecondary carriers that can be allocated by the network device 120 tothe Tx UE 110 is 16, the total quantity of bits in the second bitmappart may be 16.

In an example, the correspondence between the at least one bit in thesecond bitmap part and the at least one secondary carrier is related toa globally unique number (that is, an index) of each of the at least onesecondary carrier in the plurality of secondary carriers or theavailable carriers at the network device 120.

FIG. 14A to FIG. 16B each are a schematic diagram of a structure of thesecondary carrier setting complete information when the secondarycarrier setting complete information is used to indicate that only oneRx UE 130 has completed corresponding setting on at least onecorresponding secondary carrier. For each byte (Oct) shown in FIG. 14Ato FIG. 16B, it is assumed that bits from right to left are arrangedfrom the least significant bit to the most significant bit. In addition,SCell_(j) represents a secondary carrier whose globally unique number is

In FIG. 14A, the first bitmap part in the secondary carrier settingcomplete information includes the four most significant bits in thefirst byte (Oct 1), to indicate an index of the Rx UE 130. Assuming thatthe maximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 8, the second bitmap part mayinclude 8 bits, that is, the four least significant bits in the firstbyte (Oct 1) and the four most significant bits in the second byte (Oct2). In addition, the i^(th) bit from right to left in the four leastsignificant bits in the first byte may correspond to a secondary carrierSCell_(i)(1≤i≤4), and the i^(th) bit from right to left in the four mostsignificant bits in the second byte may correspond to a secondarycarrier SCell_(i) (5≤i≤8). In addition, in the second bitmap part, avalue of a bit that corresponds to a secondary carrier corresponding tothe Rx UE 130 may be 0 or 1, and a value of a bit that does notcorrespond to a secondary carrier corresponding to the Rx UE 130 may beN or a value other than 0 and 1.

FIG. 14B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that the Rx UE 130a in FIG. 13 has completed corresponding setting on the at least onecorresponding secondary carrier according to FIG. 14A. As shown in thefigure, the first bitmap part in the secondary carrier setting completeinformation may include an index of the Rx UE 130 a. In 8 bits in thesecond bitmap part, the least significant bit in the first byte (Oct 1)corresponds to the secondary carrier F₁ (SCell₁), and a value of the bitis 1, indicating that the Rx UE 130 a has completed correspondingsetting for an activated state of the secondary carrier F₁; the secondbit from right corresponds to the secondary carrier F₂ (SCell₂), and avalue of the bit is 0, indicating that the Rx UE 130 a has completedcorresponding setting for a deactivated state of the secondary carrierF₂; the fifth bit from right in the second byte (Oct 2) corresponds tothe secondary carrier F₈ (SCell₅), and a value of the bit is 0,indicating that the Rx UE 130 a has completed corresponding setting fora deactivated state of the secondary carrier F₅; and the eighth bit fromright in the second byte (Oct 2) corresponds to the secondary carrier F₈(SCell₈), and a value of the bit is 0, indicating that the Rx UE 130 ahas completed corresponding setting for a deactivated state of thesecondary carrier Fe. The other bits in the second bitmap part do notcorrespond to the secondary carriers corresponding to the Rx UE 130 a,and values of the bits may be N.

In FIG. 14C, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 14A. Assuming that themaximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 16, the second bitmap part mayinclude 16 bits, that is, the four least significant bits in the firstbyte (Oct 1), the second byte (Oct 2), and the four most significantbits in the third byte (Oct 3). In addition, the correspondence betweenthe four least significant bits in the first byte and secondary carriersis the same as that in FIG. 19A, the i^(th) bit from right to left inthe bits in the second byte may correspond to a secondary carrierSCell_(i+4) (1≤i≤8), and the i^(th) bit from right to left in the fourmost significant bits in the third byte may correspond to a secondarycarrier SCell_(i+8) (5≤i≤8). In addition, in the second bitmap part, avalue of a bit that corresponds to a secondary carrier corresponding tothe Rx UE 130 may be 0 or 1, and a value of a bit that does notcorrespond to a secondary carrier corresponding to the Rx UE 130 may beN or a value other than 0 and 1.

In FIG. 15A, the first bitmap part in the secondary carrier settingcomplete information includes the four least significant bits in thefirst byte (Oct 1), to indicate an index of the Rx UE 130. In addition,the four most significant bits in the first byte (Oct 1) are used asreserved bits R Assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 8,the second bitmap part may include 8 bits, that is, the second byte (Oct2). In addition, the i^(th) bit from right to left in the second byte(Oct 2) may correspond to a secondary carrier SCell_(i)(1≤i≤8). Inaddition, in the second bitmap part, a value of a bit that correspondsto a secondary carrier corresponding to the Rx UE 130 may be 0 or 1, anda value of a bit that does not correspond to a secondary carriercorresponding to the Rx UE 130 may be N or a value other than 0 and 1.Alternatively, in the first bitmap part, the four most significant bitsin the first byte (Oct 1) may be used to indicate the index of the Rx UE130, and the four least significant bits may be used as the reservedbits R.

In FIG. 15B, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 20A Assuming that themaximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 16, the second bitmap part mayinclude 16 bits, that is, the second byte (Oct 2) and the third byte(Oct 3). In addition, the correspondence between a bit in the secondbyte and a secondary carrier is the same as that in FIG. 20A, and thei^(th) bit from right to left in the third byte may correspond to asecondary carrier SCell_(i+8) (1≤i≤8). In addition, in the second bitmappart, a value of a bit that corresponds to a secondary carriercorresponding to the Rx UE 130 may be 0 or 1, and a value of a bit thatdoes not correspond to a secondary carrier corresponding to the Rx UE130 may be N or a value other than 0 and 1.

In FIG. 15C, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 15A. Assuming that themaximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 8, the second bitmap part mayinclude 8 bits, that is, the second byte (Oct 2). In addition, the leastsignificant bit in the second byte (Oct 2) is used as a reserved bit R,and the PI bit from right to left may correspond to a secondary carrierSCell_(i). (2≤i≤8). It should be noted that a quantity of secondarycarriers corresponding to the Rx UE 130 may alternatively be less than7. In this case, the second bitmap part includes bits that do notcorrespond to any secondary carrier, and values of these bits may be Nor values other than 0 and 1. Alternatively, in the first bitmap part,the four most significant bits in the first byte (Oct 1) may be used toindicate the index of the Rx UE 130, and the four least significant bitsmay be used as the reserved bits R.

In FIG. 16A, the first bitmap part in the secondary carrier settingcomplete information includes the first byte (Oct 1), the second byte(Oct 2), and the third byte (Oct 3), to indicate a destination layer-2identifier of the Rx UE 130. Assuming that the maximum quantity ofsecondary carriers that can be allocated by the network device 120 tothe Tx UE 110 is 8, the second bitmap part may include 8 bits, that is,the fourth byte (Oct 4). In addition, the correspondence between a bitin the fourth byte and a secondary carrier is the same as that in FIG.20A, and details are not described herein again. In addition, in thesecond bitmap part, a value of a bit that corresponds to a secondarycarrier corresponding to the Rx UE 130 may be 0 or 1, and a value of abit that does not correspond to a secondary carrier corresponding to theRx UE 130 may be N or a value other than 0 and 1.

In FIG. 16B, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 16A. Assuming that themaximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 16, the second bitmap part mayinclude 16 bits, that is, the fourth byte (Oct 4) and the fifth byte(Oct 5). In addition, the correspondence between a bit in the fourthbyte and the fifth byte and a secondary carrier is the same as that inFIG. 20B, and details are not described herein again. In addition, inthe second bitmap part, a value of a bit that corresponds to a secondarycarrier corresponding to the Rx UE 130 may be 0 or 1, and a value of abit that does not correspond to a secondary carrier corresponding to theRx UE 130 may be N or a value other than 0 and 1.

It should be noted that the total quantity of bits in the first bitmappart and the total quantity of bits in the second bitmap part in thesecondary carrier setting complete information are not limited to thoseshown in FIG. 14A to FIG. 16B, that is, the identifier of the Rx UE 130in the first bitmap part may occupy any quantity of bits, and the totalquantity of bits in the second bitmap part may depend on the maximumquantity of secondary carriers that can be allocated by the networkdevice 120 to the Tx UE 110 or the quantity of available carriers at thenetwork device 120. In addition, the correspondence between a bit in thesecond bitmap part and a secondary carrier is not limited to that shownin FIG. 14A to FIG. 16B either.

It should be noted that, for each byte (Oct) shown in FIG. 14A to FIG.16B, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

When the secondary carrier setting complete information is used toindicate that a plurality of Rx UEs 130 have completed correspondingsetting on corresponding secondary carriers in response to the secondsecondary carrier status indication information, the secondary carriersetting complete information may include a secondary carrier settingcomplete bitmap, and the secondary carrier setting complete bitmap mayinclude a first bitmap part and a second bitmap part. The first bitmappart may be used to indicate an identifier of each of the plurality ofRx UEs 130, for example but not limited to, an index or a destinationlayer-2 identifier of each Rx UE 130. The index of each Rx UE 130 mayinclude but is not limited to an index of each Rx UE 130 included in theforegoing destination list indication information, an index of each RxUE 130 included in the foregoing multi-carrier configuration requestinformation, an index of each Rx UE 130 having established a sidelinkconnection to the Tx UE 110, and the like. The second bitmap part may beused to indicate that each of the plurality of Rx UEs 130 has completedcorresponding setting on at least one corresponding secondary carrier inresponse to the second secondary carrier status indication information.

In an example, a total quantity of bits in the first bitmap part isrelated to a maximum quantity of Rx UEs supported by the Tx UE 110 (thatis, a maximum quantity of Rx UEs that simultaneously perform sidelinkcommunication with the Tx UE 110), a plurality of bits in the firstbitmap are in a one-to-one correspondence with the plurality of Rx UEs130, and the specific correspondence between the plurality of bits andthe plurality of Rx UEs 130 is related to the index of each Rx UE 130.

In an example, the second bitmap part may include a plurality of bitrows corresponding to the plurality of Rx UEs 130. For example,quantities of bits included in all the bit rows may be the same or maybe different. For example, the bit row may include but is not limited toa byte. The bit row is not specifically limited in this embodiment ofthis application. Each of the plurality of Rx UEs 130 corresponds to atleast one bit row, the at least one bit row includes at least one bitthat is in a one-to-one correspondence with at least one secondarycarrier, a value of each bit indicates that the Rx UE 130 has completedcorresponding setting on a secondary carrier corresponding to the bit,and the at least one secondary carrier corresponds to the Rx UE 130. Forexample, if a value of a bit in the at least one bit is 0, it indicatesthat the Rx UE 130 has completed corresponding setting for a deactivatedstate of a corresponding secondary carrier; or if a value of a bit inthe at least one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, if a value of a bit in the atleast one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for a deactivated state of a correspondingsecondary carrier: or if a value of a bit in the at least one bit is 0,it indicates that the Rx UE 130 has completed corresponding setting foran activated state of a corresponding secondary carrier. For anotherexample, when a value of a bit in the at least one bit is 0 or 1, it mayindicate that the Rx UE 130 has completed corresponding setting on asecondary carrier corresponding to the bit (not specifically indicatewhether the corresponding setting is performed for an activated state ora deactivated state).

In addition, a total quantity of bits included in the at least one bitrow may be related to a maximum quantity of secondary carriers that canbe allocated by the network device 120 to the Tx UE 110 or a quantity ofavailable carriers at the network device 120, and the correspondencebetween the at least one bit and the at least one secondary carrier isrelated to a globally unique number (that is, an index) of each of theat least one secondary carrier in the plurality of secondary carriers orthe available carriers at the network device 120.

FIG. 17A to FIG. 17C each are a schematic diagram of a structure of thesecondary carrier setting complete information when the secondarycarrier setting complete information is used to indicate that aplurality of Rx UEs 130 have completed corresponding setting oncorresponding secondary carriers in response to the second secondarycarrier status indication information. Each byte (Oct) shown in FIG. 17Ato FIG. 17C is equivalent to the foregoing one bit row. For each byte(Oct), it is assumed that bits from right to left are arranged from theleast significant bit to the most significant bit. In addition,SCell_(j) represents a secondary carrier whose globally unique number is

at the network device 120, and Rx UE_(k) represents Rx UE 130 whoseindex is “k”, where j and k are positive integers.

In FIG. 17A, assuming that the maximum quantity of Rx UEs supported bythe Tx UE 110 is 16, the first bitmap part in the secondary carriersetting complete information may include the first byte (Oct 1) and thesecond byte (Oct 2), and has a same structure as the first bitmap partin the secondary carrier setting complete information in FIG. 9A. Referto the related descriptions of FIG. 9A Details are not described hereinagain.

In FIG. 17A, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 8,in the second bitmap part in the secondary carrier setting completeinformation, each of the plurality of Rx UEs 130 corresponds to one bitrow (that is, a byte), and the specific correspondence is the same asthat in the second bitmap part in the secondary carrier setting completeinformation in FIG. 9A. Refer to the related descriptions of FIG. 9A.Details are not described herein again.

In addition, in the second bitmap part, for the byte corresponding toeach of the plurality of Rx UEs 130, the i^(th) bit from right to leftmay correspond to a secondary carrier SCell_(i) (1≤i≤8). In addition, inthe byte, a value of a bit that corresponds to a secondary carriercorresponding to the Rx UE 130 may be 0 or 1, and a value of a bit thatdoes not correspond to a secondary carrier corresponding to the Rx UE130 may be N or a value other than 0 and 1.

FIG. 17B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that the Rx UE 130a, the Rx UE 130 b, and the Rx UE 130 n in FIG. 18 have completedcorresponding setting on the corresponding secondary carriers accordingto FIG. 17A. It is assumed that an index of the Rx UE 130 a is 1, anindex of the Rx UE 130 b is 4, and an index of the Rx UE 130 n is 9. Inthis case, as shown in FIG. 17B, in the first bitmap part, values of thefirst bit and the fourth bit from right to left in the first byte(Oct 1) and the first bit from right to left in the second byte (Oct 2)are 1, and values of the other bits are 0. The second bitmap partincludes the third byte (Oct 3), the fourth byte (Oct 4), and the fifthbyte (Oct 5). For the third byte, the least significant bit correspondsto the secondary carrier F₁ (SCell₁) corresponding to the Rx UE 130 a,and a value of the bit is 1, indicating that the Rx UE 130 a hascompleted corresponding setting for an activated state of the secondarycarrier F₁; the second bit from right corresponds to the secondarycarrier F₂ (SCell₂), and a value of the bit is 0, indicating that the RxUE 130 a has completed corresponding setting for a deactivated state ofthe secondary carrier F₂; the fifth bit from right corresponds to thesecondary carrier F₅ (SCell₅), and a value of the bit is 0, indicatingthat the Rx UE 130 a has completed corresponding setting for adeactivated state of the secondary carrier F₅; the eighth bit from rightcorresponds to the secondary carrier F₈ (SCell₈), and a value of the bitis 0, indicating that the Rx UE 130 a has completed correspondingsetting for a deactivated state of the secondary carrier Fa; and theother bits do not correspond to the Rx UE 130 a, and values of the bitsmay be N. For the fourth byte, the third bit from right corresponds tothe secondary carrier F₃ (SCell₃) corresponding to the Rx UE 130 b, anda value of the bit is 0, indicating that the Rx UE 130 b has completedcorresponding setting for a deactivated state of the secondary carrierF₃; the sixth bit from right corresponds to the secondary carrier F₆(SCell₆), and a value of the bit is 1, indicating that the Rx UE 130 bhas completed corresponding setting for an activated state of thesecondary carrier F_(h); the seventh bit from right corresponds to thesecondary carrier F₇ (SCell₇), and a value of the bit is 1, indicatingthat the Rx UE 130 b has completed corresponding setting for anactivated state of the secondary carrier F₇; and the other bits do notcorrespond to the Rx UE 130 b, and values of the bits may be N. For thefifth byte, the least significant bit corresponds to the secondarycarrier F₁ (SCell₁) corresponding to the Rx UE 130 n, and a value of thebit is 1, indicating that the Rx UE 130 n has completed correspondingsetting for an activated state of the secondary carrier F₁; the fourthbit from right corresponds to the secondary carrier F₄ (SCell₄), and avalue of the bit is 1, indicating that the Rx UE 130 n has completedcorresponding setting for an activated state of the secondary carrierF₄; the sixth bit from right corresponds to the secondary carrier F₆(SCell₆), and a value of the bit is 0, indicating that the Rx UE 130 nhas completed corresponding setting for a deactivated state of thesecondary carrier F₆; the eighth bit from right corresponds to thesecondary carrier F₈ (SCell₈), and a value of the bit is 0, indicatingthat the Rx UE 130 n has completed corresponding setting for adeactivated state of the secondary carrier Fe; and the other bits do notcorrespond to the Rx UE 130 n, and values of the bits may be N.

In FIG. 17C, the first bitmap part in the secondary carrier settingcomplete information is the same as that in FIG. 17A. Assuming that themaximum quantity of secondary carriers that can be allocated by thenetwork device 120 to the Tx UE 110 is 16, in the second bitmap part,each Rx UE 130 corresponds to two bit rows (that is, bytes), and thespecific correspondence is the same as that in the second bitmap part inthe secondary carrier setting complete information in FIG. 9C. Refer tothe related descriptions of FIG. 9C. Details are not described hereinagain.

In addition, in the second bitmap part, for the two bytes correspondingto each of the plurality of Rx UEs 130, the correspondence between a bitin one byte and a secondary carrier is the same as that in FIG. 17A, andthe i^(th) bit from right to left in the bits in the other bit maycorrespond to a secondary carrier SCell_(i+8) (1≤i≤8). In addition, inthe byte, a value of a bit that corresponds to a secondary carriercorresponding to the Rx UE 130 may be 0 or 1, and a value of a bit thatdoes not correspond to a secondary carrier corresponding to the Rx UE130 may be N or a value other than 0 and 1.

It should be noted that the total quantity of bits in the first bitmappart and the total quantity of bits in the at least one bit rowcorresponding to each Rx UE 130 in the second bitmap part are notlimited to those shown in FIG. 17A to FIG. 17C. In addition, thecorrespondence between a bit in the at least one bit row correspondingto each Rx UE 130 in the second bitmap part and a secondary carrier isnot limited to that shown in FIG. 17A to FIG. 17C either.

It should be noted that, for each byte (Oct) shown in FIG. 17A to FIG.17C, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

In another example, the first bitmap part may include indexes or layer-2identifiers of the plurality of Rx UEs 130. For example, the index ofeach of the plurality of Rx UEs 130 may be an index of each Rx UE 130included in the foregoing destination list indication information, anindex of each Rx UE 130 included in the foregoing multi-carrierconfiguration request information, or an index of each Rx UE 130 havingestablished a sidelink connection to the Tx UE 110. The index of each ofthe plurality of Rx UEs 130 is not specifically limited in thisembodiment of this application. The second bitmap part may include aplurality of subparts that are in a one-to-one correspondence with theplurality of Rx UEs 130, each subpart includes at least one bit, the atleast one bit is in a one-to-one correspondence with at least onesecondary carrier, a value of each of the at least one bit may indicatethat Rx UE 130 corresponding to the subpart has completed correspondingsetting on a secondary carrier corresponding to the bit, and the atleast one secondary carrier corresponds to the Rx UE 130. For example,if a value of a bit in the at least one bit is 0, it indicates that theRx UE 130 has completed corresponding setting for a deactivated state ofa corresponding secondary carrier: or if a value of a bit in the atleast one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, if a value of a bit in the atleast one bit is 1, it indicates that the Rx UE 130 has completedcorresponding setting for a deactivated state of a correspondingsecondary carrier; or if a value of a bit in the at least one bit is 0,it indicates that the Rx UE 130 has completed corresponding setting foran activated state of a corresponding secondary carrier. For anotherexample, when a value of a bit in the at least one bit is 0 or 1, it mayindicate that the Rx UE 130 has completed corresponding setting on asecondary carrier corresponding to the bit, and the specific settingdoes not specifically indicate whether the corresponding setting isperformed for an activated state or a deactivated state.

In addition, in the second bitmap part, for each of the plurality of RxUEs 130, the correspondence between the at least one bit and the atleast one secondary carrier is related to a globally unique number (thatis, an index) of each of the at least one secondary carrier in theplurality of secondary carriers or the available carriers at the networkdevice 120.

In addition, a total quantity of bits in the second bitmap part may berelated to a maximum quantity of secondary carriers that can beallocated by the network device 120 to the Tx UE 110 or a product of aquantity of available carriers at the network device 120 and a quantityof the plurality of Rx UEs 130. For example, when the maximum quantityof secondary carriers that can be allocated by the network device 120 tothe Tx UE 110 is 8, and the quantity of the plurality of Rx UEs 130 is3, the total quantity of bits in the second bitmap part may be 24; orwhen the maximum quantity of secondary carriers that can be allocated bythe network device 120 to the Tx UE 110 is 16, and the quantity of theplurality of Rx UEs 130 is 2, the total quantity of bits in the secondbitmap part may be 32.

FIG. 18A to FIG. 20B each are a schematic diagram of a structure of thesecondary carrier setting complete information when the secondarycarrier setting complete information is used to indicate that aplurality of Rx UEs 130 have completed corresponding setting oncorresponding secondary carriers in response to the second secondarycarrier status indication information. It is assumed that bits fromright to left are arranged from the least significant bit to the mostsignificant bit. In addition, SCell_(j) represents a secondary carrierwhose globally unique number is

at the network device 120, and Rx UE_(k) represents Rx UE 130 whoseindex is “k”, where j and k are positive integers.

In FIG. 18A, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 8,the four most significant bits in the first byte (Oct 1) may be used toindicate an index of the first Rx UE 130 (Rx UE₁) in the plurality of RxUEs 130, the four least significant bits in the first byte (Oct 1) andthe four most significant bits in the second byte (Oct 2) are a subpartcorresponding to the Rx UE₁ in the second bitmap part, the i^(th) bitfrom right to left in the four least significant bits in the first byte(Oct 1) may correspond to a secondary carrier SCell (1≤i≤4), and thei^(th) bit from right to left in the four most significant bits in thesecond byte (Oct 2) may correspond to a secondary carrier SCell_(i)(5≤i≤8); the four least significant bits in the second byte (Oct 2) maybe used to indicate an index of the second Rx UE 130 (Rx UE₂) in theplurality of Rx UEs 130, the third byte (Oct 3) is a subpartcorresponding to the Rx UE₂ in the second bitmap part, and the i^(th)bit from right to left in the bits in the third byte (Oct 3) maycorrespond to a secondary carrier SCell_(i) (1≤i≤8); the four mostsignificant bits in the fourth byte (Oct 4) may be used to indicate anindex of the third Rx UE 130 (Rx UE₃) in the plurality of Rx UEs 130,the four least significant bits in the fourth byte (Oct 4) and the fourmost significant bits in the fifth byte (Oct 5) are a subpartcorresponding to the Rx UE₃ in the second bitmap part, the i^(th) bitfrom right to left in the four least significant bits in the fourth byte(Oct 4) may correspond to a secondary carrier SCell_(i) (1≤i≤4), and thei^(th) bit from right to left in the four most significant bits in thefifth byte (Oct 5) may correspond to a secondary carrier SCell_(i)(5≤i≤8): and so on, until the last Rx UE 130 in the plurality of Rx UEs130. It should be noted that, in each subpart corresponding to each RxUE 130, a value of a bit that corresponds to a secondary carriercorresponding to the Rx UE 130 may be 0 or 1, and a value of a bit thatdoes not correspond to a secondary carrier corresponding to the Rx UE130 may be N or a value other than 0 and 1.

In addition, in FIG. 18A, the first bitmap part may include the fourmost significant bits in the first byte (Oct 1), the four leastsignificant bits in the second byte (Oct 2), the four most significantbits in the fourth byte (Oct 4), and the like.

In FIG. 18B, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 16,the four most significant bits in the first byte (Oct 1) may be used toindicate an index of the first Rx UE 130 (Rx UE₁) in the plurality of RxUEs 130, the four least significant bits in the first byte (Oct 1), thesecond byte (Oct 2), and the four most significant bits in the thirdbyte (Oct 3) may be a subpart corresponding to the Rx UE₁ in the secondbitmap part, the i^(t) bit from right to left in the four leastsignificant bits in the first byte (Oct 1) may correspond to a secondarycarrier SCell_(i) (1≤i≤4), the i^(th) bit from right to left in thesecond byte (Oct 2) may correspond to a secondary carrier SCell_(i+4)(1≤i≤8), and the i^(th) bit from right to left in the four mostsignificant bits in the third byte (Oct 3) may correspond to a secondarycarrier SCell_(i+8) (5≤i≤8); the four least significant bits in thethird byte (Oct 3) may be used to indicate an index of the second Rx UE130 (Rx UE₂) in the plurality of Rx UEs 130, the fourth byte (Oct 4) andthe fifth byte (Oct 5) are a subpart corresponding to the Rx UE₂ in thesecond bitmap part, the i^(th) bit from right to left in the bits in thefourth byte (Oct 4) may correspond to a secondary carrierSCell_(i)(1≤i≤8), and the i^(th) bit from right to left in the bits inthe fifth byte (Oct 5) may correspond to a secondary carrier SCell_(i+8)(1≤i≤8); and so on, until the last Rx UE 130 in the plurality of Rx UEs130. It should be noted that, in each subpart corresponding to each RxUE 130, a value of a bit that corresponds to a secondary carriercorresponding to the Rx UE 130 may be 0 or 1, and a value of a bit thatdoes not correspond to a secondary carrier corresponding to the Rx UE130 may be N or a value other than 0 and 1.

In addition, in FIG. 18B, the first bitmap part may include the fourmost significant bits in the first byte (Oct 1), the four leastsignificant bits in the third byte (Oct 3), and the like.

In FIG. 19A, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 8,the four least significant bits in the first byte (Oct 1) may be used toindicate an index of the first Rx UE 130 (Rx UE₁) in the plurality of RxUEs 130, the four most significant bits in the first byte (Oct 1) may beused as reserved bits R, the second byte (Oct 2) may be a subpartcorresponding to the Rx UE, in the second bitmap part, and the i^(th)bit from right to left in the second byte (Oct 2) may correspond to asecondary carrier SCell_(i) (1≤i≤8); the four least significant bits inthe third byte (Oct 3) may be used to indicate an index of the second RxUE 130 (Rx UE₂ in the plurality of Rx UEs 130, the four most significantbits in the third byte (Oct 3) may be used as reserved bits R, thefourth byte (Oct 4) is a subpart corresponding to the Rx UE₂ in thesecond bitmap part, a correspondence between each bit in the fourth byteand a secondary carrier is similar to a correspondence with the Rx UE₁,and details are not described herein again; the four least significantbits in the fifth byte (Oct 5) may be used to indicate an index of thethird Rx UE 130 (Rx UE₂) in the plurality of Rx UEs 130, the four mostsignificant bits in the fifth byte (Oct 5) may be used as reserved bitsR, the sixth byte (Oct 6) is a subpart corresponding to the Rx UE₃ inthe second bitmap part, a correspondence between each bit in the sixthbyte and a secondary carrier is similar to a correspondence with the RxUE₁, and details are not described herein again; and so on, until thelast Rx UE 130 in the plurality of Rx UEs 130. It should be noted that,in each subpart corresponding to each Rx UE 130, a value of a bit thatcorresponds to a secondary carrier corresponding to the Rx UE 130 may be0 or 1, and a value of a bit that does not correspond to a secondarycarrier corresponding to the Rx UE 130 may be N or a value other than 0and 1. Alternatively, the foregoing bits used to indicate the index ofthe Rx UE 130 may be used as the reserved bits R, and the foregoingreserved bits R may be used to indicate the index of the Rx UE 130.

In addition, in FIG. 19A, the first bitmap part may include the fourleast significant bits in the first byte (Oct 1), the four leastsignificant bits in the third byte (Oct 3), the four least significantbits in the fifth byte (Oct 5), and the like.

In FIG. 19B, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 8,the four least significant bits in the first byte (Oct 1) may be used toindicate an index of the first Rx UE 130 (Rx UE₁) in the plurality of RxUEs 130, the four most significant bits in the first byte (Oct 1) may beused as reserved bits R, the second byte (Oct 2) and the third byte (Oct3) are a subpart corresponding to the Rx UE₁ in the second bitmap part,the i^(th) bit from right to left in the second byte (Oct 2) maycorrespond to a secondary carrier SCell_(i) (1≤i≤8), and the i^(th) bitfrom right to left in the bits in the third byte (Oct 3) may correspondto a secondary carrier SCell_(i+8) (1≤i≤8); the four least significantbits in the fourth byte (Oct 4) may be used to indicate an index of thesecond Rx UE 130 (Rx UE₂) in the plurality of Rx UEs 130, the four mostsignificant bits in the fourth byte (Oct 4) may be used as reserved bitsR, the fifth byte (Oct 5) and the sixth byte (Oct 6) are a subpartcorresponding to the Rx UE₂ in the second bitmap part, a correspondencebetween each bit in the fifth byte and the sixth byte and a secondarycarrier is similar to a correspondence with the Rx UE₁, and details arenot described herein again; the four least significant bits in theseventh byte (Oct 7) may be used to indicate an index of the third Rx UE130 (Rx UE₃) in the plurality of Rx UEs 130, the four most significantbits in the seventh byte (Oct 7) may be used as reserved bits R, theeighth byte (Oct 8) and the ninth byte (Oct 9) are a subpartcorresponding to the Rx UE: in the second bitmap part, a correspondencebetween each bit in the eighth byte and the ninth byte and a secondarycarrier is similar to a correspondence with the Rx UE₁, and details arenot described herein again; and so on, until the last Rx UE 130 in theplurality of Rx UEs 130. It should be noted that, in each subpartcorresponding to each Rx UE 130, a value of a bit that corresponds to asecondary carrier corresponding to the Rx UE 130 may be 0 or 1, and avalue of a bit that does not correspond to a secondary carriercorresponding to the Rx UE 130 may be N or a value other than 0 and 1.Alternatively, the foregoing bits used to indicate the index of the RxUE 130 may be used as the reserved bits R. and the foregoing reservedbits R may be used to indicate the index of the Rx UE 130.

In addition, in FIG. 19B, the first bitmap part may include the fourleast significant bits in the first byte (Oct 1), the four leastsignificant bits in the fourth byte (Oct 4), the four least significantbits in the seventh byte (Oct 7), and the like.

In FIG. 20A, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 8,the first byte (Oct 1) to the third byte (Oct 3) may be used to indicatea destination layer-2 identifier of the first Rx UE 130 (Rx UE₁) in theplurality of Rx UEs 130, the fourth byte (Oct 4) is a subpartcorresponding to the Rx UE₁ in the second bitmap part, and the i^(th)bit from right to left in the fourth byte (Oct 4) may correspond to asecondary carrier SCell_(i) (1≤i≤8); the fifth byte (Oct 5) to theseventh byte (Oct 7) may be used to indicate a destination layer-2identifier of the second Rx UE 130 (Rx UE₂) in the plurality of Rx UEs130, the eighth byte (Oct 8) is a subpart corresponding to the Rx UE₂ inthe second bitmap part, a correspondence between each bit in the eightbyte and a secondary carrier is similar to a correspondence with the RxUE₁, and details are not described herein again; and so on, until thelast Rx UE 130 in the plurality of Rx UEs 130. It should be noted that,in each subpart corresponding to each Rx UE 130, a value of a bit thatcorresponds to a secondary carrier corresponding to the Rx UE 130 may be0 or 1, and a value of a bit that does not correspond to a secondarycarrier corresponding to the Rx UE 130 may be N or a value other than 0and 1.

In addition, in FIG. 20A, the first bitmap part may include the firstbyte (Oct 1) to the third byte (Oct 3), the fifth byte (Oct 5) to theseventh byte (Oct 7), and the like.

In FIG. 20B, assuming that the maximum quantity of secondary carriersthat can be allocated by the network device 120 to the Tx UE 110 is 16,the first byte (Oct 1) to the third byte (Oct 3) may be used to indicatea destination layer-2 identifier of the first Rx UE 130 (Rx UE₁) in theplurality of Rx UEs 130, the fourth byte (Oct 4) and the fifth byte (Oct5) are a subpart corresponding to the Rx UE₁ in the second bitmap part,the i^(th) bit from right to left in the fourth byte (Oct 4) maycorrespond to a secondary carrier SCell; (1≤i≤8), and the i^(th) bitfrom right to left in the fifth byte (Oct 5) may correspond to asecondary carrier SCell_(i+8) (1≤i≤8); the sixth byte (Oct 6) to theeighth byte (Oct 8) may be used to indicate a destination layer-2identifier of the second Rx UE 130 (Rx UE₂) in the plurality of Rx UEs130, the ninth byte (Oct 9) and the tenth byte (Oct 10) are a subpartcorresponding to the Rx UE₂ in the second bitmap part, a correspondencebetween each bit in the ninth byte and the tenth byte and a secondarycarrier is similar to a correspondence with the Rx UE₁, and details arenot described herein again; and so on, until the last Rx UE 130 in theplurality of Rx UEs 130. It should be noted that, in each subpartcorresponding to each Rx UE 130, a value of a bit that corresponds to asecondary carrier corresponding to the Rx UE 130 may be 0 or 1, and avalue of a bit that does not correspond to a secondary carriercorresponding to the Rx UE 130 may be N or a value other than 0 and 1.

In addition, in FIG. 20B, the first bitmap part may include the firstbyte (Oct 1) to the third byte (Oct 3), the sixth byte (Oct 6) to theeighth byte (Oct 8), and the like.

It should be noted that, in the first bitmap part in the secondarycarrier setting complete information, the identifier of each of theplurality of Rx UEs 130 may occupy any quantity of bits, and thequantity is not limited to that shown in FIG. 10A to FIG. 12B; and inthe second bitmap part, the total quantity of bits in each subpartcorresponding to each of the plurality of Rx UEs 130 is not limited tothat shown in FIG. 18A to FIG. 20B either. In addition, thecorrespondence between each bit in each subpart and a secondary carrieris not limited to that shown in FIG. 18A to FIG. 20B either.

It should be noted that, for each byte (Oct) shown in FIG. 18A to FIG.20B, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

It should be noted that the secondary carrier setting completeinformation having the foregoing structure in this embodiment may beused in S317 in FIG. 3A to FIG. 3C.

Embodiment 3

In this embodiment, the network device 120 performs globally non-uniquenumbering on the plurality of secondary carriers indicated in the firstmulti-carrier configuration information. The globally non-uniquenumbering means that the network device 120 performs global numbering onthe plurality of secondary carriers, and each of the plurality ofsecondary carriers may have at least one number. In this case, Rx UE 130corresponding to a secondary carrier can be determined based on aglobally non-unique number of the secondary carrier. Therefore, the TxUE 110 does not need to add an identifier of the Rx UE 130 to thesecondary carrier setting complete information.

It should be noted that, in this embodiment, that the network device 120performs globally non-unique numbering on the plurality of secondarycarriers indicated in the first multi-carrier configuration informationis related to S308 in FIG. 3A to FIG. 3C, and the secondary carriersetting complete information is related to S317 in FIG. 3A to FIG. 3C.

Numbering Performed by the Network Device 120 and the Tx UE 110 on theSecondary Carriers

FIG. 21 shows an example of carrier allocation at the network device 120and an example of performing globally non-unique numbering by thenetwork device 120 on the carriers and performing local numbering orglobally non-unique numbering by the Tx UE 110 on the carriers. As shownin FIG. 21 , it is assumed that the plurality of secondary carriersallocated to the Tx UE 110 at the network device 120 include F₁, F₂, F₃,F₄, F₅, F₆, F₇, and F₈. Specifically, F₁, F₂, F₅, and F₈ are used by theTx UE 110 to perform sidelink communication with the Rx UE 130 a; F₃,F₆, and F₇ are used by the Tx UE 110 to perform sidelink communicationwith the Rx UE 130 b; and F₁, F₄, F₆, and F₈ are used by the Tx UE 110to perform sidelink communication with the Rx UE 130 n.

In an example, the network device 120 may perform globally non-uniquenumbering in an arrangement order of the identifiers of the plurality ofsecondary carriers in the first multi-carrier configuration information.For example, assuming that the arrangement order of the secondarycarriers corresponding to the Rx UE 130 a, the Rx UE 130 b, and the RxUE 130 n in the first multi-carrier configuration information is F₁, F₂,F₅, F₅, F₃, F₆, F₇, F₁, F₄, F₆, and F₈, as shown in FIG. 26 , globallynon-unique numbers of F₁, F₂, F₅, F₈, F₃, F₆, F₇, F₁, F₄, F₆, and F₈that are sequentially arranged by the network device 120 may berespectively “{circle around (1)}”, “{circle around (2)}”, “{circlearound (3)}”, “{circle around (4)}”, “{circle around (5)}”, “{circlearound (6)}”, “{circle around (7)}”, “{circle around (8)}”, “{circlearound (9)}”, “{circle around (10)}”, and “{circle around (11)}”.

It should be noted that carrier allocation at the network device 120 isnot limited to that shown in FIG. 21 , and the network device 120 mayalternatively perform globally non-unique numbering on the plurality ofsecondary carriers according to any other appropriate rule.

In addition, local numbering performed by the network device 120 on theplurality of secondary carriers may be used in S308 in FIG. 3A to FIG.3C, and the network device 120 may indicate the globally non-uniquenumbers of the plurality of secondary carriers in the firstmulti-carrier configuration information. However, when there is aglobally non-unique numbering rule between the Tx UE 110 and the networkdevice 120 by default, the network device 120 may alternatively notindicate the globally non-unique numbers of the plurality of secondarycarriers in the first multi-carrier configuration information. Forexample, the globally non-unique numbering rule may be performingglobally non-unique numbering in the arrangement order of theidentifiers of the plurality of secondary carriers in the firstmulti-carrier configuration information, for example, “{circle around(1)}”, “{circle around (2)}”, “{circle around (3)}”, “{circle around(4)}”, “{circle around (5)}”, “{circle around (6)}”, “{circle around(7)}”, “{circle around (8)}”, “{circle around (9)}”, “{circle around(10)}”, and “{circle around (11)}”. The globally non-unique numberingrule is not limited in this embodiment of this application.

Secondary Carrier Setting Complete Information

The secondary carrier setting complete information may include asecondary carrier setting complete bitmap, to indicate that each of theat least one Rx UE 130 has completed corresponding setting of the atleast one corresponding secondary carrier in response to the secondsecondary carrier status indication information.

In an example, the secondary carrier setting complete bitmap includes atleast one bitmap part, the at least one bitmap part is in a one-to-onecorrespondence with the at least one Rx UE 130, each of the at least onebitmap part includes at least one bit, the at least one bit is in aone-to-one correspondence with the at least one secondary carrier, avalue of each of the at least one bit indicates that Rx UE 130corresponding to the bitmap part has completed corresponding setting ona secondary carrier corresponding to the bit, and the at least onesecondary carrier corresponds to the Rx UE 130. For example, if a valueof a bit is 0, it indicates that the Rx UE 130 has completedcorresponding setting for a deactivated state of a correspondingsecondary carrier; or if a value of a bit is 1, it indicates that the RxUE 130 has completed corresponding setting for an activated state of acorresponding secondary carrier. For another example, if a value of abit is 1, it indicates that the Rx UE 130 has completed correspondingsetting for a deactivated state of a corresponding secondary carrier; orif a value of a bit is 0, it indicates that the Rx UE 130 has completedcorresponding setting for an activated state of a correspondingsecondary carrier. For another example, when a value of a bit in the atleast one bit is 0 or 1, it may indicate that the Rx UE 130 hascompleted corresponding setting on a secondary carrier corresponding tothe bit (not specifically indicate whether the corresponding setting isperformed for an activated state or a deactivated state).

In an example, a total quantity of bits in the at least one bit part isrelated to a total quantity of secondary carriers corresponding to theat least one Rx UE 130, and the total quantity of secondary carrierscorresponding to the at least one Rx UE 130 is equal to a sum ofquantities of the at least one secondary carrier corresponding to allthe Rx UEs 130.

In an example, an arrangement order of each bitmap part in the secondarycarrier setting complete bitmap is related to an index of each Rx UE130, and the correspondence between the at least one bit in each bitmappart and the at least one secondary carrier is related to a globallynon-unique number of the at least one secondary carrier at the networkdevice 120.

FIG. 22A to FIG. 22C each are a schematic diagram of a structure of thesecondary carrier setting complete information. For each byte (Oct)shown in FIG. 22A to FIG. 22C, it is assumed that bits from right toleft are arranged from the least significant bit to the most significantbit. In addition, SCell_(j) represents a secondary carrier whoseglobally non-unique number is “{circle around (j)}” at the networkdevice 120, and Rx UE_(k) represents Rx UE 130 whose index is “k”, wherej and k are positive integers.

In FIG. 22A, the four least significant bits in the first byte (Oct 1)may be a bitmap part corresponding to Rx UE₁, and the four leastsignificant bits in the first byte (Oct 1) are arranged from right toleft; the fifth to seventh bits from right to left in the first byte(Oct 1) may be a bitmap part corresponding to Rx UE₂, and the fifth toseventh bits from right to left in the first byte (Oct 1) mayrespectively correspond to secondary carriers SCell₅ to SCell₇corresponding to the Rx UE₂; and the most significant bit in the firstbyte (Oct 1) and the three least significant bits in the second byte(Oct 2) may be a bitmap part corresponding to Rx UE₃, the mostsignificant bit in the first byte (Oct 1) may correspond to a secondarycarrier SCell₈ corresponding to the Rx UE₃, and the three leastsignificant bits in the second byte (Oct 2) may respectively correspondto secondary carriers SCell₉ to SCell₁₁ corresponding to the Rx UEs. Itshould be noted that division of each bitmap part in the secondarycarrier setting complete bitmap is not limited to that shown in FIG.22A.

FIG. 22B is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that the Rx UE 130a, the Rx UE 130 b, and the Rx UE 130 n in FIG. 21 have completedcorresponding setting on the corresponding secondary carriers accordingto FIG. 22A. It is assumed that an index of the Rx UE 130 a is 1, anindex of the Rx UE 130 b is 2, and an index of the Rx UE 130 n is 3. Inthis case, the four least significant bits in the first byte (Oct 1)correspond to the Rx UE 130 a. Specifically, the least significant bitin the first byte (Oct 1) corresponds to a secondary carrier F₁(SCell_(i)) whose globally non-unique number is “1”, and a value of thebit is 1, indicating that the Rx UE 130 a has completed correspondingsetting for an activated state of the secondary carrier F₁; the secondbit from right corresponds to a secondary carrier F₂ (SCell₂) whoseglobally non-unique number is “2”, and a value of the bit is 0,indicating that the Rx UE 130 a has completed corresponding setting fora deactivated state of the secondary carrier F₂; the third bit fromright corresponds to a secondary carrier F₅ (SCell₃) whose globallynon-unique number is “{circle around (3)}”, and a value of the bit is 1,indicating that the Rx UE 130 a has completed corresponding setting foran activated state of the secondary carrier F₅; and the fourth bit fromright corresponds to a secondary carrier F₈ (SCell₄) whose globallynon-unique number is “{circle around (4)}”, and a value of the bit is 0,indicating that the Rx UE 130 a has completed corresponding setting fora deactivated state of the secondary carrier F₅, The fifth to seventhbits from right to left in the first byte (Oct 1) correspond to the RxUE 130 b. Specifically, the fifth bit from right to left in the firstbyte (Oct 1) corresponds to a secondary carrier F₃ (SCell₅) whoseglobally non-unique number is “{circle around (5)}”, and a value of thebit is 0, indicating that the Rx UE 130 b has completed correspondingsetting for a deactivated state of the secondary carrier F₃; the sixthbit from right corresponds to a secondary carrier F₆ (SCell₆) whoseglobally non-unique number is “0”, and a value of the bit is 1,indicating that the Rx UE 130 b has completed corresponding setting foran activated state of the secondary carrier F₆; and the seventh bit fromright corresponds to a secondary carrier F₇ (SCell₇) whose globallynon-unique number is “0”, and a value of the bit is 1, indicating thatthe Rx UE 130 b has completed corresponding setting for an activatedstate of the secondary carrier F₇. The most significant bit in the firstbyte (Oct 1) and the three least significant bits in the second byte(Oct 2) may correspond to the Rx UE 130 n. Specifically, the mostsignificant bit in the first byte (Oct 1) may correspond to a secondarycarrier F₁ (SCell₈) whose globally non-unique number is “{circle around(8)}”, and a value of the bit is 1, indicating that the Rx UE 130 n hascompleted corresponding setting for an activated state of the secondarycarrier F₁; the least significant bit in the second byte (Oct 2)corresponds to a secondary carrier F₄ (SCell₉) whose globally non-uniquenumber is “{circle around (9)}”, and a value of the bit is 1, indicatingthat the Rx UE 130 n has completed corresponding setting for anactivated state of the secondary carrier F₄; the second bit from rightcorresponds to a secondary carrier F₆ (SCell₁₀) whose globallynon-unique number is “{circle around (8)}”, and a value of the bit is 0,indicating that the Rx UE 130 n has completed corresponding setting fora deactivated state of the secondary carrier F₆; and the third bit fromright corresponds to a secondary carrier F₈ (SCell₁₁) whose globallynon-unique number is “{circle around (11)}”, and a value of the bit is0, indicating that the Rx UE 130 n has completed corresponding settingfor a deactivated state of the secondary carrier F₈.

FIG. 22C is a schematic diagram of a structure of the secondary carriersetting complete information that is used to indicate that the Rx UE 130a and the Rx UE 130 n in FIG. 21 have completed corresponding setting onthe corresponding secondary carriers according to FIG. 22A. It isassumed that an index of the Rx UE 130 a is 1, an index of the Rx UE 130b is 2, and an index of the Rx UE 130 n is 3. In this case, the fourleast significant bits in the first byte (Oct 1) correspond to the Rx UE130 a. For a specific correspondence, refer to the related descriptionsin FIG. 22B. The fifth to seventh bits from right to left in the firstbyte (Oct 1) correspond to the Rx UE 130 b. When the secondary carriersetting complete information does not indicate activated states ordeactivated states of the secondary carriers corresponding to the Rx UE130 b at the Tx UE 110, values of the fifth to seventh bits from rightto left in the first byte (Oct 1) may be N or values other than 0 and 1.The most significant bit in the first byte (Oct 1) and the three leastsignificant bits in the second byte (Oct 2) may correspond to the Rx UE130 n. For a specific correspondence, refer to the related descriptionsin FIG. 22B.

It should be noted that, for each byte (Oct) shown in FIG. 22A to FIG.22C, it may alternatively be assumed that bits from right to left arearranged from the most significant bit to the least significant bit. Inthis case, the foregoing embodiment is still applicable.

It should be noted that the secondary carrier setting completeinformation having the foregoing structure in this embodiment may beused in S317 in FIG. 3A to FIG. 3C.

Embodiment 4

When corresponding Rx UE 130 can be uniquely determined by using anidentifier of a secondary carrier, for example, when the identifier ofthe secondary carrier is the foregoing globally non-unique number, thesecondary carrier setting complete information may include an identifierof a secondary carrier on which each of one or more Rx UEs 130 hascompleted corresponding setting for an activated state, or an identifierof a secondary carrier on which each Rx UE 130 has completedcorresponding setting for a deactivated state. The identifier of thesecondary carrier may include but is not limited to an ID, a cell index,a number, and the like of the secondary carrier.

For example, assuming that the network device 120 configures SCell₁,SCell₂, and SCell₃ for the Rx UE 130 a, where SCell₁ and SCell₂ each areconfigured to be in an activated state, and SCell₁ is configured to bein a deactivated state, the secondary carrier setting completeinformation may include globally non-unique numbers of SCell₁ andSCell₂. Therefore, the network device 120 can learn that the Rx UE 130 ahas completed corresponding setting for the activated states of SCell₁and SCell₂ and corresponding setting for the deactivated state ofSCell₃.

When corresponding Rx UE 130 cannot be uniquely determined by using anidentifier of a secondary carrier, for example, when the identifier ofthe secondary carrier is the foregoing local number or globally uniquenumber, the secondary carrier setting complete information may includeidentifiers of one or more Rx UEs 130, and an identifier of a secondarycarrier on which each Rx UE 130 has completed corresponding setting foran activated state, or an identifier of a secondary carrier on whicheach Rx UE 130 has completed corresponding setting for a deactivatedstate. For example, the identifier of each of the one or more Rx UEs 130may be an index of the Rx UE 130 or a destination layer-2 identifier ofthe Rx UE 130. The identifier of each of the one or more Rx UEs 130 isnot specifically limited in this embodiment of this application. Theidentifier of the secondary carrier may include but is not limited to anID, a cell index, a number, and the like of the secondary carrier.

For example, assuming that the network device 120 configures SCell₁,SCell₂, and SCell₃ for the Rx UE 130 a, where SCell₁ and SCell₂ each areconfigured to be in an activated state, and SCell₃ is configured to bein a deactivated state, the secondary carrier setting completeinformation may include a destination layer-2 identifier of the Rx UE130 a and a local number or a globally unique number of SCell₃.Therefore, the network device 120 can learn that the Rx UE 130 a hascompleted corresponding setting for the deactivated state of SCell₃ andcorresponding setting for the activated states of SCell₁ and SCell₂.

It should be noted that the secondary carrier setting completeinformation having the foregoing structure in this embodiment may beused in S317 in FIG. 3A to FIG. 3C.

Embodiment 5

The secondary carrier setting complete information may includeidentifiers of one or more Rx UEs 130 from which the Tx UE 110 receivesthe second acknowledgment information, for example but not limited to, adestination layer-2 identifier (destination layer-2 ID) or an index ofthe Rx UE 130. The index of the Rx UE 130 may include but is not limitedto an index of each Rx UE 130 included in the foregoing destination listindication information, an index of each Rx UE 130 included in theforegoing multi-carrier configuration request information, an index ofeach Rx UE 130 having established a sidelink connection to the Tx UE110, and the like.

It should be noted that the secondary carrier setting completeinformation having the foregoing structure in this embodiment may beused in S317 in FIG. 3A to FIG. 3C.

FIG. 23A and FIG. 23B are a schematic flowchart of a wirelesscommunication method 2300 applied to Tx UE 110 according to anembodiment of this application. In the method 2300, steps performed bythe Tx UE 110 include the steps related to the Tx UE 110 in FIG. 3A toFIG. 3C.

It should be noted that, although steps of the method are presented in aparticular order in this embodiment of this application, the order ofthe steps may be changed in different embodiments. As shown in FIG. 23Aand FIG. 23B, the wireless communication method 2300 may include thefollowing steps.

S2301: The Tx UE 110 sends sidelink communication requirement indicationinformation to a network device 120. For this step, refer to thedescriptions of S301 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2302: Receive, from the network device 120, information indicating thata resource allocation mode of the Tx UE 110 is a base station scheduledresource allocation mode. For this step, refer to the descriptions ofS302 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2303: Send, to the network device 120, information for requestingresources required for sidelink connection establishment. For this step,refer to the descriptions of S303 in FIG. 3A to FIG. 3C. Details are notdescribed herein again.

S2304: Receive, from the network device 120, information indicatingresources scheduled by the network device 120 for the Tx UE 110. Forthis step, refer to the descriptions of S304 in FIG. 3A to FIG. 3C.Details are not described herein again.

S2305: Send sidelink connection establishment request information to oneor more Rx UEs 130 based on the resources allocated by the networkdevice 120. For this step, refer to the descriptions of S305 in FIG. 3Ato FIG. 3C. Details are not described herein again.

S2306: Receive sidelink connection establishment complete indicationinformation from the one or more Rx UEs 130. For this step, refer to thedescriptions of S306 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2307: When there is data to be transmitted to the Rx UE 130, sendsidelink radio bearer establishment request information andmulti-carrier configuration request information to the network device120 by using a third message. For this step, refer to the descriptionsof S307 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2308: Receive information indicating a radio bearer configured by thenetwork device 120 for the Tx UE 110 and first multi-carrierconfiguration information from the network device 120. For this step,refer to the descriptions of S308 in FIG. 3A to FIG. 3C. Details are notdescribed herein again.

S2309: Send second multi-carrier configuration information to the one ormore Rx UEs 130. For this step, refer to the descriptions of S309 inFIG. 3A to FIG. 3C. Details are not described herein again.

S2310: Receive multi-carrier configuration complete indicationinformation from the one or more Rx UEs 130. For this step, refer to thedescriptions of S310 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2311: Send the multi-carrier configuration complete indicationinformation to the network device 120. For this step, refer to thedescriptions of S311 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2312: Send, to the network device 120, information for requestingresources required for data transmission. For this step, refer to thedescriptions of S312 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2313: Receive first secondary carrier status indication informationfrom the network device 120. For this step, refer to the descriptions ofS313 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2314: Send first acknowledgment information to the network device 120,to indicate, to the network device 120, that the first secondary carrierstatus indication information is received from the network device 120.

For this step, refer to the descriptions of S314 in FIG. 3A to FIG. 3C.Details are not described herein again.

S2315: Send second secondary carrier status indication information tothe one or more Rx UEs 130. For this step, refer to the descriptions ofS315 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2316: Receive second acknowledgment information from one or more Rx UEs130, to indicate, to the Tx UE 110, that the one or more Rx UEs 130 havereceived the second secondary carrier status indication information fromthe Tx UE 110.

For this step, refer to the descriptions of S316 in FIG. 3A to FIG. 3C.Details are not described herein again.

S2317: Send secondary carrier setting complete information to thenetwork device 120 by using a tenth message, to indicate, to the networkdevice 120, that one or more Rx UEs 130 have completed correspondingsetting on corresponding secondary carriers in response to the secondsecondary carrier status indication information.

For this step, refer to the descriptions of S317 in FIG. 3A to FIG. 3C.Details are not described herein again.

FIG. 24 is a schematic flowchart of a wireless communication method 2400applied to a network device 120 according to an embodiment of thisapplication. In the method 2400, steps performed by the network device120 include the steps related to the network device 120 in FIG. 3A toFIG. 3C.

It should be noted that, although steps of the method are presented in aparticular order in this embodiment of this application, the order ofthe steps may be changed in different embodiments. As shown in FIG. 24 ,the wireless communication method 2400 may include the following steps:

S2401: Receive sidelink communication requirement indication informationfrom Tx UE 110. For this step, refer to the descriptions of S241 in FIG.3A to FIG. 3C. Details are not described herein again.

S2402: Send, to the Tx UE 110, information indicating that a resourceallocation mode of the Tx UE 110 is a base station scheduled resourceallocation mode. For this step, refer to the descriptions of S242 inFIG. 3A to FIG. 3C. Details are not described herein again.

S2403: Receive, from the Tx UE 110, information for requesting resourcesrequired for sidelink connection establishment. For this step, refer tothe descriptions of S243 in FIG. 3A to FIG. 3C. Details are notdescribed herein again.

S2404: Send, to the Tx UE 110, information indicating resourcesscheduled by the network device 120 for the Tx UE 110. For this step,refer to the descriptions of S244 in FIG. 3A to FIG. 3C. Details are notdescribed herein again.

S2405: Receive sidelink radio bearer establishment request informationand multi-carrier configuration request information from the Tx UE 110.For this step, refer to the descriptions of S247 in FIG. 3A to FIG. 3C.Details are not described herein again.

S2406: Send information indicating a radio bearer configured by thenetwork device 120 for the Tx UE 110 and first multi-carrierconfiguration information to the Tx UE 110. For this step, refer to thedescriptions of S248 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2407: Receive multi-carrier configuration complete indicationinformation from the Tx UE 110. For this step, refer to the descriptionsof S311 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2408: Receive, from the Tx UE 110, information for requesting resourcesrequired for data transmission. For this step, refer to the descriptionsof S312 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2409: Generate first secondary carrier status indication informationand send the first secondary carrier status indication information tothe Tx UE 110. For this step, refer to the descriptions of S313 in FIG.3A to FIG. 3C. Details are not described herein again.

S2410: Receive first acknowledgment information from the Tx UE 110,where the first acknowledgment information is used by the Tx UE 110 toindicate, to the network device 120, that the first secondary carrierstatus indication information is received from the network device 120.For this step, refer to the descriptions of S314 in FIG. 3A to FIG. 3C.Details are not described herein again.

S2411: Receive secondary carrier setting complete information from theTx UE 110, where the secondary carrier setting complete information isused by the Tx UE 110 to indicate, to the network device 120, that oneor more Rx UEs 130 have completed corresponding setting on correspondingsecondary carriers in response to the second secondary carrier statusindication information.

For this step, refer to the descriptions of S317 in FIG. 3A to FIG. 3C.Details are not described herein again.

FIG. 25 is a schematic flowchart of a wireless communication method 2500applied to Rx UE 130 according to an embodiment of this application. Inthe method 2500, steps performed by the Rx UE 130 include the stepsrelated to the Rx UE 130 in FIG. 3A to FIG. 3C.

It should be noted that, although steps of the method are presented in aparticular order in this embodiment of this application, the order ofthe steps may be changed in different embodiments. As shown in FIG. 25 ,the wireless communication method 2500 may include the following steps:

S2501: Receive sidelink connection establishment request informationfrom Tx UE 110. For this step, refer to the descriptions of S305 in FIG.3A to FIG. 3C. Details are not described herein again.

S2502: Send sidelink connection establishment complete indicationinformation to the Tx UE 110. For this step, refer to the descriptionsof S306 in FIG. 3A to FIG. 3C. Details are not described herein again.

S2503: Receive second multi-carrier configuration information from theTx UE 110. For this step, refer to the descriptions of S309 in FIG. 3Ato FIG. 3C. Details are not described herein again.

S2504: Perform setting based on the second multi-carrier configurationinformation from the Tx UE 110, to perform sidelink communication on atleast one corresponding secondary carrier. For this step, refer to thedescriptions of S250 in FIG. 3A to FIG. 3C. Details are not describedherein again.

S2505: Send multi-carrier configuration complete indication informationto the Tx UE 110. For this step, refer to the descriptions of S250 inFIG. 3A to FIG. 3C. Details are not described herein again.

S2506: Receive second secondary carrier status indication informationfrom the Tx UE 110. For this step, refer to the descriptions of S254 inFIG. 3A to FIG. 3C. Details are not described herein again.

S2507: Send second acknowledgment information to the Tx UE 110 toacknowledge that the second secondary carrier status indicationinformation is received from the Tx UE 110.

For this step, refer to the descriptions of S316 in FIG. 3A to FIG. 3C.Details are not described herein again.

In this embodiment of this application, a procedure required formulti-carrier sidelink communication between the Tx UE 110 and the Rx UE130 is defined. In addition, the Tx UE 110 performs sidelinkcommunication by using a plurality of carriers, and resources for datatransmission increase. Even if the Tx UE 110 has a large datacommunication requirement, communication quality of the Tx UE 110 can beensured.

Further, concepts of a primary carrier and a secondary carrier areintroduced in this embodiment of this application. The primary carrieris used to establish a sidelink connection between the Tx UE 110 and theRx UE 130, and the secondary carrier is used to provide an additionalradio resource. Division of the primary carrier and the secondarycarrier helps control sidelink communication between the Tx UE 110 andthe Rx UE 130.

Further, the network device 120 may indicate an activated state or adeactivated state of each secondary carrier to the Tx UE 110, and asecondary carrier activation or deactivation mechanism can better managebattery consumption of the Rx UE 130.

Further, the Tx UE 110 sends reception user equipment carrier settingcomplete information to the network device 120, so that the networkdevice 120 can be prevented from starting data scheduling before the RxUE 130 completes setting on a corresponding carrier.

FIG. 26 is a schematic module diagram of a device 2600 according to anembodiment of this application. The device 2600 may include the Tx UE110, the network device 120, and the Rx UE 130 in the foregoingembodiments.

In some embodiments, the device 2600 may include at least an applicationcircuit 2602, a baseband circuit 2604, a radio frequency (RF) circuit2606, a front end module (FEM) circuit 2608, and one or more antennas2610 that coupled together, as shown in the figure. The components ofthe device 2600 may be included in UE. For example, the applicationcircuit 2602 may be included in a processor 102 of UE 10, and thebaseband circuit 2604, the radio frequency (RF) circuit 2606, the frontend module (FEM) circuit 2608, and the one or more antennas 2610 may beincluded in a communications module 104 of the UE 10. In someembodiments, the device 2600 may include fewer elements. In someembodiments, the device 2600 may include additional elements, such as amemory/storage device, a display, a camera, a sensor, or an input/output(I/O) interface.

The application circuit 2602 may include one or more applicationprocessors. For example, the application circuit 2602 may include acircuit, for example but not limited to, one or more single-core ormulti-core processors. The (one or more) processors may include anycombination of a general-purpose processor and a special-purposeprocessor (for example, a graphics processing unit or an applicationprocessor). The processor may be coupled to the memory/storage apparatusor may include the memory/storage apparatus, and may be configured torun instructions stored in the memory/storage apparatus, so that thedevice 2600 can implement any one or more methods described withreference to FIG. 3A to FIG. 3C to FIG. 15 . The instructions stored inthe memory/storage apparatus may include: when the instructions are runby the processor, the device 2600 is enabled to implement any one ormore methods described with reference to FIG. 3A to FIG. 3C to FIG. 15 .

The baseband circuit 2604 may include a circuit, for example but notlimited to, one or more single-core or multi-core processors. Thebaseband circuit 2604 may include one or more baseband processors orcontrol logic, to process a baseband signal received from a signalreceiving path of the RF circuit 2606 and generate a baseband signalused for a signal sending path of the RF circuit 2606. The basebandprocessing circuit 2604 may interface with the application circuit 2602to generate and process a baseband signal and control an operation ofthe RF circuit 2606. For example, in some embodiments, the basebandcircuit 2604 may include a third generation (3G) baseband processor2604A, a fourth generation (4G) baseband processor 2604B, a fifthgeneration (5G) baseband processor 2604C, or (one or more) otherbaseband processors 2604D used in another existing generation, indevelopment, or in a to-be-developed generation in the future (forexample, a sixth generation (6G)). The baseband circuit 2604 (forexample, one or more of the baseband processors 2604A to D) may processvarious radio control functions that support communication with one ormore radio networks through the RF circuit 2606. In another embodiment,some or all functions of the baseband processors 2604A to D may beincluded in a module stored in the memory 2604G, and these functions maybe performed by using a central processing unit (CPU) 2604E. The radiocontrol functions may include but are not limited to signalmodulation/demodulation, encoding/decoding, radio frequency shift, andthe like. In some embodiments, the modulation/demodulation circuit ofthe baseband circuit 2604 may include fast Fourier transform (FFT),precoding, and/or constellation mapping/demapping functions. In someembodiments, the encoding/decoding circuit of the baseband circuit 2604may include convolution, tail biting (tail-biting) convolution, turbo,Viterbi (Viterbi), and/or low-density parity-check (LDPC)encoder/decoder functions. Embodiments of the modulation/demodulationand encoder/decoder functions are not limited to these examples, andother appropriate functions may be included in other embodiments.

In some embodiments, the baseband circuit 2604 may include one or moreaudio digital signal processors (DSP) 2604F. The (one or more) audioDSPs 2604F may include elements for compression/decompression and echocancellation, and may include other appropriate processing elements inother embodiments. In some embodiments, the components of the basebandcircuit may be appropriately combined in a single chip, a single chipset, or arranged on a same circuit board. In some embodiments, some orall of the components of the baseband circuit 2604 and the applicationcircuit 2602 may be implemented together, for example, on asystem-on-a-chip (SOC).

In some embodiments, the baseband circuit 2604 may provide communicationcompatible with one or more radio technologies. For example, in someembodiments, the baseband circuit 2604 may support communication with anevolved universal terrestrial radio access network (E-UTRAN) or anotherwireless metropolitan area network (WMAN), a wireless local area network(WLAN), or a wireless personal area network (WPAN). An embodiment inwhich the baseband circuit 2604 is configured to support radiocommunication of more than one wireless protocol may be referred to as amulti-mode baseband circuit.

The RF circuit 2606 may support communication with a wireless networkthrough modulated electromagnetic radiation by using a non-solid medium.In various embodiments, the RF circuit 2606 may include a switch, afilter, an amplifier, and the like to assist in communication with thewireless network. The RF circuit 2606 may include a signal receivingpath. The signal receiving path may include a circuit that performsdown-conversion on an RF signal received from the FEM circuit 2608 andprovides a baseband signal for the baseband circuit 2604. The RF circuit2606 may further include a signal sending path. The signal sending pathmay include a circuit that performs up-conversion on a baseband signalprovided by the baseband circuit 2604 and provides an RF output signalfor the FEM circuit 2608 for transmission.

In some embodiments, the signal receiving path of the RF circuit 2606may include a mixer circuit 2606 a, an amplifier circuit 2606 b, and afilter circuit 2606 c. In some embodiments, the signal sending path ofthe RF circuit 2606 may include a filter circuit 2606 c and a mixercircuit 2606 a. The RF circuit 2606 may further include a synthesizercircuit 2606 d. The synthesizer circuit is configured to synthesizefrequencies for use by the mixer circuits 2606 a of the signal receivingpath and the signal sending path. In some embodiments, the mixer circuit2606 a of the signal receiving path may be configured to perform, basedon a synthesized frequency provided by the synthesizer circuit 2606 d,down-conversion on an RF signal received from the FEM circuit 2608. Theamplifier circuit 2606 b may be configured to amplify a down-convertedsignal, and the filter circuit 2606 c may be a low-pass filter (LPF) ora bandpass filter (BPF) configured to remove an unwanted signal from thedown-converted signal to generate an output baseband signal. The outputbaseband signal may be provided for the baseband circuit 2604 forfurther processing. In some embodiments, the output baseband signal maybe a zero-frequency baseband signal, but this is not required. In someembodiments, the mixer circuit 2606 a of the signal receiving path mayinclude a passive mixer, but the scope of the embodiment is not limitedin this regard.

In some embodiments, the mixer circuit 2606 a of the signal sending pathmay be configured to perform up-conversion on an input baseband signalbased on a synthesized frequency provided by the synthesizer circuit2606 d, to generate an RF output signal for the FEM circuit 2608. Thebaseband signal may be provided by the baseband circuit 2604, and thefilter circuit 2606 c may perform filtering on the baseband signal.

In some embodiments, the mixer circuit 2606 a of the signal receivingpath and the mixer circuit 2606 a of the signal sending path may includetwo or more mixers, and may be arranged for orthogonal down-conversionand/or up-conversion respectively.

In some embodiments, the mixer circuit 2606 a of the signal receivingpath and the mixer circuit 2606 a of the signal sending path may includetwo or more mixers, and may be arranged for image rejection (forexample, Hartley image rejection). In some embodiments, the mixercircuit 2606 a of the signal receiving path and the mixer circuit 2606 aof the signal sending path may be arranged for direct down-conversionand/or direct up-conversion respectively. In some embodiments, the mixercircuit 2606 a of the signal receiving path and the mixer circuit 2606 aof the signal sending path may be configured to perform asuperheterodyne operation.

In some embodiments, the output baseband signal and the input basebandsignal may be analog baseband signals, but the scope of the embodimentis not limited in this regard. In some alternative embodiments, theoutput baseband signal and the input baseband signal may be digitalbaseband signals. In these alternative embodiments, the RF circuit 2606may include an analog-to-digital converter (ADC) circuit and adigital-to-analog converter (DAC) circuit, and the baseband circuit 2604may include a digital baseband interface to communicate with the RFcircuit 2606.

In some dual-mode embodiments, a separate radio IC circuit may beprovided to process a signal of each spectrum, but the scope of theembodiment is not limited in this regard.

In some embodiments, the synthesizer circuit 2606 d may be a fractionalN-type synthesizer or a fractional N/N+1 type synthesizer, but the scopeof the embodiment is not limited in this regard because other types offrequency synthesizers may be appropriate. For example, the synthesizercircuit 2606 d may be a delta-sigma synthesizer, a frequency multiplier,or a synthesizer that includes a phase-locked loop with a frequencydivider.

The synthesizer circuit 2606 d may be configured to synthesize, based ona frequency input and a frequency divider control input, an outputfrequency for use by the mixer circuit 2606 a of the RF circuit 2606. Insome embodiments, the synthesizer circuit 2606 d may be a fractionalN/N+1 type synthesizer.

In some embodiments, the frequency input may be provided by avoltage-controlled oscillator (VCO), but this is not required. Thefrequency divider control input may be provided by the baseband circuit2604 or the application processor 2602 based on a required outputfrequency. In some embodiments, the frequency divider control input (forexample, N) may be determined from a lookup table based on a channelindicated by the application processor 2602.

The synthesizer circuit 2606 d of the RF circuit 2606 may include afrequency divider, a delay-locked loop (DLL), a multiplexer, and a phaseaccumulator. In some embodiments, the frequency divider may be adual-mode frequency divider (DMD), and the phase accumulator may be adigital phase accumulator (DPA). In some embodiments, the DMD may beconfigured to divide an input signal by N or N+1 (for example, based ona carry output) to provide a fractional division ratio. In some exampleembodiments, the DLL may include a cascaded set of tunable delayelements, a phase detector, a charge pump, and a D-type flip-flop. Inthese embodiments, the delay elements may be configured to decompose aVCO cycle into a maximum of Nd equal phase groups, where Nd is aquantity of delay elements in a delay line. In this way, the DLLprovides negative feedback to help ensure that a total delay through thedelay line is one VCO cycle.

In some embodiments, the synthesizer circuit 2606 d may be configured togenerate a carrier frequency as an output frequency. However, in otherembodiments, the output frequency may be a multiple of the carrierfrequency (for example, twice the carrier frequency or four times thecarrier frequency) and used with a quadrature generator and a frequencydivider circuit to generate a plurality of signals with different phasesat the carrier frequency. In some embodiments, the output frequency maybe an LO frequency (fLO). In some embodiments, the RF circuit 2606 mayinclude an IQ/polarity converter.

The FEM circuit 2608 may include a signal receiving path, and the signalreceiving path may include a circuit configured to: operate an RF signalreceived from the one or more antennas 2610, amplify the receivedsignal, and provide an amplified version of the received signal for theRF circuit 2606 for further processing. The FEM circuit 2608 may furtherinclude a signal sending path, and the signal sending path may include acircuit configured to amplify a signal that is provided by the RFcircuit 2606 and that is used for transmission, so that the signal istransmitted by one or more of the one or more antennas 2610. In variousembodiments, amplification through the signal sending path or the signalreceiving path may be completed only in the RF circuit 2606, only in theFEM 2608, or in both the RF circuit 2606 and the FEM 2608.

In some embodiments, the FEM circuit 2608 may include a TX/RX switch, toswitch between transmit mode and receive mode operations. The FEMcircuit may include a signal receiving path and a signal sending path.The signal receiving path of the FEM circuit may include a low noiseamplifier (LNA) to amplify the received RF signal and provide theamplified received RF signal as an output (for example, to the RFcircuit 2606). The signal sending path of the FEM circuit 2608 mayinclude a power amplifier (PA) configured to amplify an input RF signal(for example, provided by the RF circuit 2606) and one or more filtersconfigured to generate an RF signal for subsequent transmission (forexample, through one or more of the one or more antennas 2610).

Although this application is described with reference to exampleembodiments, this does not mean that features of the present inventionare limited only to the implementations. On the contrary, a purpose ofdescribing the present invention with reference to the implementationsis to cover other selections or modifications that may be derived basedon the claims of this application. To provide an in-depth understandingof this application, the following descriptions include a plurality ofspecific details. This application may be alternatively implementedwithout using these details. In addition, to avoid confusion or blurringthe focus of this application, some specific details are omitted fromthe descriptions. It should be noted that embodiments in thisapplication and the features in embodiments may be mutually combined ina case of no conflict.

In addition, various operations are described as a plurality of discreteoperations in a manner that is most conducive to understandingillustrative embodiments. However, an order described should not beconstrued as implying that these operations need to depend on the order.In particular, these operations do not need to be performed in therendered order.

As used herein, a term “module” or “unit” may mean, be, or include: anapplication-specific integrated circuit (ASIC), an electronic circuit, a(shared, special-purpose, or group) processor and/or a memory thatexecutes one or more software or firmware programs, a composite logiccircuit, and/or another appropriate component that provides thedescribed functions.

In the accompanying drawings, some structure or method features may beshown in a particular arrangement and/or order. However, it should beunderstood that such a particular arrangement and/or order may not berequired. In some embodiments, these features may be arranged in amanner and/or order different from that shown in the illustrativeaccompanying drawings. In addition, inclusion of the structure or methodfeatures in a particular figure does not imply that such features arerequired in all embodiments. In some embodiments, these features may notbe included or may be combined with other features.

Embodiments of a mechanism disclosed in this application may beimplemented by hardware, software, firmware, or a combination of theseimplementations. Embodiments of this application may be implemented as acomputer program or program code executed in a programmable system. Theprogrammable system includes a plurality of processors, a storage system(including a volatile memory, a nonvolatile memory, and/or a storageelement), a plurality of input devices, and a plurality of outputdevices.

The program code may be used to input instructions, to perform functionsdescribed in this application and generate output information. Theoutput information may be applied to one or more output devices in aknown manner. For a purpose of this application, a processing systemincludes any system having a processor such as a digital signalprocessor (DSP), a microcontroller, an application-specific integratedcircuit (ASIC), or a microprocessor.

The program code may be implemented by using a high-level programminglanguage or an object-oriented programming language, to communicate withthe processing system. The program code may also be implemented by usingan assembly language or a machine language when needed. Actually, themechanism described in this application is not limited to a scope of anyparticular programming language. In any case, the language may be acompiled language or an interpretive language.

In some cases, the disclosed embodiments may be implemented by hardware,firmware, software, or any combination thereof. In some cases, one ormore aspects of at least some embodiments may be implemented byexpressive instructions, stored in a computer-readable storage medium.The instructions represent various types of logic in a processor, andwhen the instructions are read by a machine, the machine is enabled tomanufacture logic for performing the technologies described in thisapplication. These representations referred to as “IP cores” may bestored in a tangible computer-readable storage medium, and provided fora plurality of customers or production facilities for loading into amanufacturing machine that actually manufactures the logic or theprocessor.

Such a computer-readable storage medium may include but is not limitedto non-transient tangible arrangements of articles manufactured orformed by machines or devices. The computer-readable storage mediumincludes a storage medium, for example, a hard disk or any other type ofdisk including a floppy disk, a compact disc, a compact disc read-onlymemory (CD-ROM), a compact disc rewritable (CD-RW), or a magneto-opticaldisc; a semiconductor device, for example, a read-only memory (ROM) suchas a random access memory (RAM) including a dynamic random access memory(DRAM) or a static random access memory (SRAM), an erasable programmableread-only memory (EPROM), a flash memory, or an electrically erasableprogrammable read-only memory (EEPROM); a phase change memory (PCM); amagnetic card or an optical card; or any other type of appropriatemedium for storing electronic instructions.

Therefore, embodiments of this application further include anon-transient computer-readable storage medium. The medium includesinstructions or design data, for example, a hardware descriptionlanguage (HDL), and defines a structure, a circuit, an apparatus, aprocessor, and/or a system feature described in this application.

With reference to the foregoing descriptions, this application furtherprovides the following embodiments:

Embodiment 1: A wireless communication method applied to transmissionuser equipment (Tx UE) is provided, and the method includes:

receiving first secondary carrier (SCell) status indication informationfrom a network device, where the first secondary carrier statusindication information indicates that each of a plurality of secondarycarriers is in an activated state or a deactivated state, the pluralityof secondary carriers are used for multi-carrier sidelink communicationbetween the transmission user equipment and at least one reception userequipment, and each of the at least one reception user equipmentcorresponds to at least one of the plurality of secondary carriers;

sending second secondary carrier status indication information to eachreception user equipment, where the second secondary carrier statusindication information indicates that each of the at least one secondarycarrier is in an activated state or a deactivated state; and

when acknowledgment information is received from one or more of the atleast one reception user equipment, sending secondary carrier settingcomplete information to the network device, where the acknowledgmentinformation is used to indicate that the one or more reception userequipments have received the second secondary carrier status indicationinformation, and the secondary carrier setting complete information isused to indicate that the one or more reception user equipments havecompleted corresponding setting on the at least one secondary carrier.

Embodiment 2: According to the method in Embodiment 1, the methodfurther includes:

when the acknowledgment information is not received from the one or morereception user equipments, sending secondary carrier setting incompleteinformation to the network device, where the secondary carrier settingincomplete information is used to partially indicate at least that theone or more reception user equipments do not complete the correspondingsetting in response to the second secondary carrier status indicationinformation.

Embodiment 3: According to the method in Embodiment 1 or 2, the methodfurther includes:

receiving first multi-carrier configuration information from the networkdevice, where the first multi-carrier configuration informationindicates information related to the plurality of secondary carriersconfigured by the network device, and the first multi-carrierconfiguration information includes an identifier of each reception userequipment and an identifier of the at least one secondary carriercorresponding to each reception user equipment in the plurality ofsecondary carriers; and

sending second multi-carrier configuration information to each receptionuser equipment based on the first multi-carrier configurationinformation, where the second multi-carrier configuration informationincludes the identifier of the at least one secondary carriercorresponding to each reception user equipment.

Embodiment 4: According to the method in any one of Embodiments 1 to 3,when the one or more reception user equipments include first receptionuser equipment, the secondary carrier setting complete informationincludes a first bitmap part that is used to indicate an identifier ofthe first reception user equipment and a second bitmap part that is usedto indicate that the first reception user equipment has completed thecorresponding setting.

Embodiment 5: According to the method in Embodiment 4, the identifier ofthe first reception user equipment includes a destination layer-2identifier (destination layer-2 ID) of the first reception userequipment or an index of the first reception user equipment.

Embodiment 6: According to the method in Embodiment 4 or 5, at least onebit in the second bitmap part is in a one-to-one correspondence with theat least one secondary carrier, a value of each of the at least one bitindicates that the first reception user equipment has completed thecorresponding setting, and the corresponding setting is performed on asecondary carrier corresponding to each bit in the at least onesecondary carrier.

Embodiment 7: According to the method in any one of Embodiments 4 to 6,a total quantity of bits in the second bitmap part is related to amaximum quantity of secondary carriers supported by the first receptionuser equipment or the transmission user equipment.

Embodiment 8: According to the method in any one of Embodiments 4 to 7,the correspondence between the at least one bit in the second bitmappart and the at least one secondary carrier is related to an arrangementorder of the identifier of the at least one secondary carrier in thefirst multi-carrier configuration information.

Embodiment 9: According to the method in any one of Embodiments 4 to 7,the correspondence between the at least one bit in the second bitmappart and the at least one secondary carrier is related to an index ofeach of the at least one secondary carrier in the plurality of secondarycarriers.

Embodiment 10: According to the method in any one of Embodiments 1 to 9,the method further includes:

requesting, from the network device, an uplink resource used to send thesecondary carrier setting complete information.

Embodiment 11: According to the method in any one of Embodiments 1 to10, the secondary carrier setting complete information is sent by usinga resource reserved by the network device.

Embodiment 12: A wireless communication method applied to a networkdevice is provided, and the method includes:

generating first secondary carrier status indication information, wherethe first secondary carrier status indication information indicates thateach of a plurality of secondary carriers is in an activated state or adeactivated state, the plurality of secondary carriers are used formulti-carrier sidelink communication between transmission user equipmentand at least one reception user equipment, and each of the at least onereception user equipment corresponds to at least one of the plurality ofsecondary carriers;

sending the first secondary carrier status indication information to thetransmission user equipment (Tx UE); and

receiving secondary carrier setting complete information from thetransmission user equipment, where the secondary carrier settingcomplete information is used to indicate that each of one or morereception user equipments has completed corresponding setting on the atleast one secondary carrier, and the at least one reception userequipment includes the one or more reception user equipments.

Embodiment 13: According to the method in Embodiment 12, the methodfurther includes:

sending first multi-carrier configuration information to thetransmission user equipment, where the first multi-carrier configurationinformation indicates information related to the plurality of secondarycarriers configured by the network device, and the first multi-carrierconfiguration information includes an identifier of each reception userequipment and an identifier of the at least one secondary carriercorresponding to each reception user equipment in the plurality ofsecondary carriers.

Embodiment 14: According to the method in Embodiment 12 or 13,

when the one or more reception user equipments include first receptionuser equipment, the secondary carrier setting complete informationincludes a first bitmap part that is used to indicate an identifier ofthe first reception user equipment and a second bitmap part that is usedto indicate that the first reception user equipment has completed thecorresponding setting.

Embodiment 15: According to the method in Embodiment 14, the identifierof the first reception user equipment includes a destination layer-2identifier (destination layer-2 ID) of the first reception userequipment or an index of the first reception user equipment.

Embodiment 16: According to the method in Embodiment 14 or 15, at leastone bit in the second bitmap part is in a one-to-one correspondence withthe at least one secondary carrier, a value of each of the at least onebit indicates that the first reception user equipment has completed thecorresponding setting, and the corresponding setting is performed on asecondary carrier corresponding to each bit in the at least onesecondary carrier.

Embodiment 17: According to the method in any one of Embodiments 14 to16, a total quantity of bits in the second bitmap part is related to amaximum quantity of secondary carriers supported by the first receptionuser equipment or the transmission user equipment.

Embodiment 18: According to the method in any one of Embodiments 14 to17, the correspondence between the at least one bit in the second bitmappart and the at least one secondary carrier is related to an arrangementorder of the identifier of the at least one secondary carrier in thefirst multi-carrier configuration information, or is related to an indexof each of the at least one secondary carrier in the plurality ofsecondary carriers.

Embodiment 19: According to the method in any one of Embodiments 12 to18, the method further includes:

receiving, from the transmission user equipment, a request for an uplinkresource used to send the secondary carrier setting completeinformation.

Embodiment 20: A machine-readable medium is provided. The medium storesinstructions, and when the instructions are run on a machine, themachine is enabled to perform the method in any one of Embodiments 1 to19.

Embodiment 21: A device is provided, including:

a processor: and

a memory, where the memory stores instructions, and when theinstructions are run on the processor, the system is enabled to performthe method in any one of Embodiments 1 to 19.

Embodiment 22: A communications system is provided, including atransmission user equipment and a network device, where

the network device is configured to generate first secondary carrierstatus indication information and send the first secondary carrierstatus indication information to the transmission user equipment, wherethe first secondary carrier status indication information indicates thateach of a plurality of secondary carriers is in an activated state or adeactivated state, the plurality of secondary carriers are used formulti-carrier sidelink communication between the transmission userequipment and at least one reception user equipment, and each of the atleast one reception user equipment corresponds to at least one of theplurality of secondary carriers; and

the transmission user equipment is configured to: receive the firstsecondary carrier status indication information, and send secondsecondary carrier status indication information to each reception userequipment, where the second secondary carrier status indicationinformation indicates that each of the at least one secondary carrier isin an activated state or a deactivated state; and

when acknowledgment information is received from one or more of the atleast one reception user equipment, send secondary carrier settingcomplete information to the network device, where the acknowledgmentinformation is used to indicate that the one or more reception userequipments have received the second secondary carrier status indicationinformation, and the secondary carrier setting complete information isused to indicate that each of the one or more reception user equipmentshas completed corresponding setting on the at least one secondarycarrier.

1-27. (canceled)
 28. A wireless communication method implemented by afirst user equipment and comprising: receiving first secondary carrierstatus indication information from a network device, wherein the firstsecondary carrier status indication information indicates that each of aplurality of secondary carriers is in an activated state or adeactivated state, the secondary carriers are for multi-carrier sidelinkcommunication between the first user equipment and at least one seconduser equipment, and each second user equipment corresponds to at leastone of the secondary carriers; sending second secondary carrier statusindication information to each second user equipment, wherein the secondsecondary carrier status indication information indicates that eachsecondary carrier is in an activated state or a deactivated state; andsending, when receiving acknowledgment information from one or more ofthe at least one second user equipment, secondary carrier settingcomplete information to the network device, wherein the acknowledgmentinformation indicates that the one or more second user equipments havereceived the second secondary carrier status indication information, andwherein the secondary carrier setting complete information indicatesthat each of the one or more second user equipments has completed acorresponding setting on at least one of the secondary carriers.
 29. Thewireless communication method according to claim 28, further comprisingsending, when not receiving the acknowledgment information from the oneor more second user equipments, secondary carrier setting incompleteinformation to the network device, wherein the secondary carrier settingincomplete information partially indicates that the one or more seconduser equipments do not complete the corresponding setting in response tothe second secondary carrier status indication information.
 30. Thewireless communication method according to claim 28, further comprising:receiving first multi-carrier configuration information from the networkdevice, wherein the first multi-carrier configuration informationindicates information related to the secondary carriers configured bythe network device, and wherein the first multi-carrier configurationinformation comprises a first identifier of each second user equipmentand a second identifier of at least one of the secondary carrierscorresponding to each second user equipment; and sending secondmulti-carrier configuration information to each second user equipmentbased on the first multi-carrier configuration information, wherein thesecond multi-carrier configuration information comprises the secondidentifier.
 31. The wireless communication method according to claim 28,wherein when the secondary carriers are for multi-carrier sidelinkcommunication between the first user equipment and a plurality of seconduser equipments, the secondary carrier setting complete informationcomprises a first bitmap part that indicates an index or a destinationlayer-2 identifier of each second user equipment and a second bitmappart indicates that each second user equipment has completed thecorresponding setting.
 32. The wireless communication method accordingto claim 28, wherein the secondary carrier setting complete informationcomprises a secondary carrier setting complete bitmap that indicatesthat each of the one or more second user equipments has completed thecorresponding setting.
 33. The wireless communication method accordingto claim 28, wherein the secondary carrier setting complete informationcomprises: first identifiers of the one or more second user equipmentsand second identifiers of the secondary carriers for which the one ormore second user equipments have completed the corresponding setting forthe activated state or the deactivated state; or the second identifiers.34. A wireless communication method implemented by a network device andcomprising: generating first secondary carrier status indicationinformation, wherein the first secondary carrier status indicationinformation indicates that each of a plurality of secondary carriers isin an activated state or a deactivated state, the secondary carriers arefor multi-carrier sidelink communication between a first user equipmentand at least one second user equipment, and each second user equipmentcorresponds to at least one of the secondary carriers; sending the firstsecondary carrier status indication information to the first userequipment; and receiving secondary carrier setting complete informationfrom the first user equipment, wherein the secondary carrier settingcomplete information indicates that each of one or more second userequipments has completed a corresponding setting on at least one of thesecondary carriers.
 35. The wireless communication method according toclaim 34, further comprising sending first multi-carrier configurationinformation to the first user equipment, wherein the first multi-carrierconfiguration information indicates information related to the secondarycarriers configured by the network device, and wherein the firstmulti-carrier configuration information comprises a first identifier ofeach second user equipment and a second identifier of at least one ofthe secondary carriers corresponding to each second user equipment. 36.The wireless communication method according to claim 35, wherein whenthe secondary carriers are for multi-carrier sidelink communicationbetween the first user equipment and a plurality of second userequipments, the secondary carrier setting complete information comprisesa first bitmap part that indicates an index or a destination layer-2identifier of each second user equipment and a second bitmap part thatindicates that each second user equipment has completed thecorresponding setting.
 37. The wireless communication method accordingto claim 36, wherein a total quantity of bits in the first bitmap partis related to a maximum quantity of second user equipments supported bythe first user equipment, wherein one or more bits in the first bitmappart are in a one-to-one correspondence with the one or more second userequipments, and wherein the one-to-one correspondence is related to theindex of each second user equipment.
 38. The wireless communicationmethod according to claim 36, wherein the second bitmap part comprises aplurality of bit rows corresponding to the plurality of second userequipments, wherein each second user equipment corresponds to at leastone of the bit rows that comprises at least one bit in a one-to-onecorrespondence with one secondary carrier, and wherein a value of the atleast one bit indicates that the corresponding second user equipment hascompleted the corresponding setting on the secondary carrier.
 39. Thewireless communication method according to claim 38, wherein a totalquantity of bits in the at least one of the bit rows is related to amaximum quantity of secondary carriers supported by each second userequipment or the first user equipment.
 40. The wireless communicationmethod according to claim 38, wherein the one-to-one correspondence isrelated to an arrangement order of an identifier of at least one of thesecondary carriers in the first multi-carrier configuration informationor to an index of each secondary carrier.
 41. The wireless communicationmethod according to claim 35, wherein the secondary carrier settingcomplete information comprises a secondary carrier setting completebitmap that indicates that each of the one or more second user equipmenthas completed the corresponding setting.
 42. The wireless communicationmethod according to claim 41, wherein the secondary carrier settingcomplete bitmap comprises at least one bitmap part in a correspondencewith the one or more second user equipments, wherein each bitmap partcomprises at least one bit in a one-to-one correspondence with onesecondary carrier, and wherein a value of the at least one bit indicatesthat the corresponding second user equipment has completed thecorresponding setting on the secondary carrier.
 43. The wirelesscommunication method according to claim 42, wherein a first totalquantity of bits in the at least one bitmap part is related to a secondtotal quantity of secondary carriers corresponding to the one or moresecond user equipments, and wherein the second total quantity ofsecondary carriers is equal to a sum of quantities of the secondarycarriers corresponding to a sum of the one or more second userequipments.
 44. The wireless communication method according to claim 42,wherein a first arrangement order of each bitmap part is related to asecond arrangement order of an identifier of each second user equipmentin the first multi-carrier configuration information, and wherein theone-to-one correspondence is related to the second arrangement.
 45. Thewireless communication method according to claim 41, further comprising:performing monitoring setting on a secondary carrier that is indicatedto be in the activated state; or performing de-monitoring setting on asecondary carrier that is indicated to be in the deactivated state. 46.The wireless communication method according to claim 34, wherein thesecondary carrier setting complete information comprises: firstidentifiers of the one or more second user equipments and secondidentifiers of the secondary carriers for which the one or more seconduser equipments have completed the corresponding setting for theactivated state or the deactivated state; or the second identifiers. 47.A computer program product comprising computer-executable instructionsthat are stored on a non-transitory computer-readable storage medium andthat, when executed by a processor, cause a first user equipment to:receive first secondary carrier status indication information from anetwork device, wherein the first secondary carrier status indicationinformation indicates that each of a plurality of secondary carriers isin an activated state or a deactivated state, the secondary carriers arefor multi-carrier sidelink communication between the first userequipment and at least one second user equipment, and each second userequipment corresponds to at least one of the secondary carriers; sendsecond secondary carrier status indication information to each seconduser equipment, wherein the second secondary carrier status indicationinformation indicates that each secondary carrier is in an activatedstate or a deactivated state; and send, when acknowledgment informationis received from the at least one second user equipment, secondarycarrier setting complete information to the network device, wherein theacknowledgment information indicates that the at least one second userequipment has received the second secondary carrier status indicationinformation, and wherein the secondary carrier setting completeinformation indicates that each second user equipment has completed acorresponding setting on at least one of the secondary carriers.